From eating you alive? Metabolism is down to 10% of normal conditions and almost all of our enzymes have an optimum around 310 K (37 Degrees C). Immune cells won't be very active in hibernation (282 K, 11 degrees C), while some microorganisms flourish at that temperature. Just put a piece of cheese in your fridge, wait two months and take a look to see what the effects can be.
Actually there's probably already a couple of billion of them on your skin and completely sterilizing a human being (alive) is long from possible. Six hours of hibernation is one thing, but I wouldn't want to try this for more than a day.
Since insulin is a relatively small polypeptide, wouldn't it be easier on the patient to grow the beta-cells on substrate inside microspheres with pores of about 50 nm? If you make the spheres out of non-organic material, immune cells will neither attack them or move into them.
ASCII art:
/-o-\ / i \ i / \ | csc | o csc io c = beta cells | csc | s = substrate (serum proteins) o csc o o = pore \ / i = insulin o / i \_o_/
The insulin and glucose can traverse the pores, but immune cells can't reach the beta cells.
Just some wild speculation and it probably isn't even practical. I'm just a biochemist.
An unknown spyware vendor has been funding the research and is now starting to dredge up keylog files with negative timestamps. "They never refused to accept our EULA ", Spokesman S. Ucker commented.
It's from the days when BlueGene/L was still relatively small, but the basic design hasn't changed since then.
Turns out it's split into I/O and computing nodes. The 1024 I/O nodes run Linux. Each controls 64 dual-cpu nodes, which use simplistic microkernels written from scratch using Linux as an example.
The network architecture sounds funky: apparantly it's based on a torus!
"but planet vs stars: stars have fusion, planets dont"
It's not that simple. If one follows your definition, the earth would have become a star when the first hydrogen bomb exploded.
Actually the Medical Physiology intitute at my univerity is working on growing organs from stem cells in vitro. Extremities will probably be possible as well, but all this won't be practical for at least half a century.
If the downforce of all that ice disappears into the oceans, the tectonic plate might start to balance itself, causing giant earthquakes while lowering the US and Canada.
The same thing happened to Scandinavia after the last ice age.
It's difficult to predict exactly what will happen and how strongly, but it's a dangerous possibility you don't hear much about.
A few years ago, when Phoenix was first released, I was among the first to try it. Pleased by its relative stability, speed and overall lightweight character, I started using it as my primary browser. Later releases brought further improvements, like extensions. Fast forward to 2004:
Side-effects: - Firefox is very unstable compared to Phoenix - The development team has started linking Firefox against glibc 2.3
The improvements are of little to no benefit IMHO: - Auto-update is too unreliable and impractical when you're not root. It's actually quicker to do it the old-fashioned way - Being a slightly conservative bastard who can't appreciate eye candy if it isn't female, I've never used skins. - The improved search is an exception. The colours are handy if you're visually scanning a large document and it eliminates the window blocking your view. It's actually a bit like vim's search. - The download manager is not very practical. It gives clueless lusers a harder time infecting their PC's, but it's "hidden" into the browser and the actions surrounding a download take more time now than ever before.
The decay which has been accompanying all this development is quite severe:
- The stability issues cause two crashes on an average day for me. Some sites actually cause crashes whenever viewed. In most cases the sites contain buggy html and javacrypt, but that should not crash the browser. Notable examples include WebCT and requested popups.
- Although most modern distros use glibc 2.3, I'm not going to switch for a while. I've tried setting up a chroot for it, but the latest version of gcc appears to be unable to compilethe latest glibc.
According to the gcc maintainers this is a bug in glibc.
According to the glibc maintainers this is a bug in gcc.
blah rant rave curse slap stab blam, etc
Even though there's a hack to get it working, I'm staying with glibc 2.2 until both groups have stopped trying to break eachother's code.
But there's always PLAN B. And after three hours of compiling firefox 1.0, it turns out that the degradation curve since 0.8 has not changed course.
Some common sense inhibitor snaps in my skull and I ditch firefox. Alternatives:
Konqueror toy Dillo incomplete Links rules my console, but it has some
inherent disabilities etcetcetc.
But there's always the "dead" Mozilla. It turns out that Mozilla is not as dead as commonly thought.
Mozilla has become much lighter nowadays. The e-mail, news and chat is seperated from the browser package now and doesn't swallow memory anymore and it's noticeably faster than before. It can also use extensions, block popups and evil javascript code, and some other features we've started to like about Firefox. Among the differences are a more intuitive download manager and unfortunately the old text search. But the most important differences are its much greater stability and the fact that it is backwards compatible with glibc 2.2 and possibly even older versions.
So, contrary to the mainstream momentum, I've switched back to Mozilla. Getting it working took a few mouseclicks instead of a full compile and minutes instead of hours. I live happily ever after.
If you're having nervous breakdowns with firefox, consider this move.
Slashdot Mirror
From eating you alive? Metabolism is down to 10% of normal conditions and almost all of our enzymes have an optimum around 310 K (37 Degrees C). Immune cells won't be very active in hibernation (282 K, 11 degrees C), while some microorganisms flourish at that temperature. Just put a piece of cheese in your fridge, wait two months and take a look to see what the effects can be.
Actually there's probably already a couple of billion of them on your skin and completely sterilizing a human being (alive) is long from possible. Six hours of hibernation is one thing, but I wouldn't want to try this for more than a day.
Since insulin is a relatively small polypeptide, wouldn't it be easier on the patient to grow the beta-cells on substrate inside microspheres with pores of about 50 nm? If you make the spheres out of non-organic material, immune cells will neither attack them or move into them.
/-o-\
ASCII art:
/ i \ i
/ \
| csc |
o csc io c = beta cells
| csc | s = substrate (serum proteins)
o csc o o = pore
\ / i = insulin
o / i
\_o_/
The insulin and glucose can traverse the pores, but immune cells can't reach the beta cells.
Just some wild speculation and it probably isn't even practical. I'm just a biochemist.
An unknown spyware vendor has been funding the research and is now starting to dredge up keylog files with negative timestamps. "They never refused to accept our EULA ", Spokesman S. Ucker commented.
There are details in an article somewhere on the net.
Gosh, that certainly sounds like a source reliable enough for these kinds of predictions.
Apparently even genes are magically aware* of the benefits of diversity.
*deliberate oversimplification
Here's an article describing some of the specs.
/ gupta.pdf
http://www.llnl.gov/asci/platforms/bluegene/talks
It's from the days when BlueGene/L was still relatively small, but the basic design hasn't changed since then.
Turns out it's split into I/O and computing nodes. The 1024 I/O nodes run Linux. Each controls 64 dual-cpu nodes, which use simplistic microkernels written from scratch using Linux as an example.
The network architecture sounds funky: apparantly it's based on a torus!
"but planet vs stars: stars have fusion, planets dont" It's not that simple. If one follows your definition, the earth would have become a star when the first hydrogen bomb exploded.
Actually the Medical Physiology intitute at my univerity is working on growing organs from stem cells in vitro. Extremities will probably be possible as well, but all this won't be practical for at least half a century.
What if all the ice on Greenland melts? It doesn't float, so it will make the sea level rise. By seven meters, according to current estimates
To make matters worse, greenland is on the far end of the
North American plate.
If the downforce of all that ice disappears into the oceans, the tectonic plate might start to balance itself, causing giant earthquakes while lowering the US and Canada.
The same thing happened to Scandinavia after the last ice age.
It's difficult to predict exactly what will happen and how strongly, but it's a dangerous possibility you don't hear much about.
Military spy satellites have always been superior in both resolution, contrast-to-noise-ratio and magnification to their non-military counterparts.
Now these previously secret optics technology are partially out in the open, what will be done with them?
I'm sure they could be used to greatly improve the imaging resolution of space probes for example.
(After an elusive secret society of slashdot users uses it for a frikkin earth-blasting-laser that is)
A few years ago, when Phoenix was first released, I was among the first to try it. Pleased by its relative stability, speed and overall lightweight character, I started using it as my primary browser. Later releases brought further improvements, like extensions. Fast forward to 2004:
Improvements:
- Auto-update
- Improved search
- Skin
- Download manager
Side-effects:
- Firefox is very unstable compared to Phoenix
- The development team has started linking Firefox against glibc 2.3
The improvements are of little to no benefit IMHO:
- Auto-update is too unreliable and impractical when you're not root. It's actually quicker to do it the old-fashioned way
- Being a slightly conservative bastard who can't appreciate eye candy if it isn't female, I've never used skins.
- The improved search is an exception. The colours are handy if you're visually scanning a large document and it eliminates the window blocking your view. It's actually a bit like vim's search.
- The download manager is not very practical. It gives clueless lusers a harder time infecting their PC's, but it's "hidden" into the browser and the actions surrounding a download take more time now than ever before.
The decay which has been accompanying all this development is quite severe:
- The stability issues cause two crashes on an average day for me. Some sites actually cause crashes whenever viewed. In most cases the sites contain buggy html and javacrypt, but that should not crash the browser. Notable examples include WebCT and requested popups.
- Although most modern distros use glibc 2.3, I'm not going to switch for a while.
I've tried setting up a chroot for it, but the latest version of gcc appears to be unable to compilethe latest glibc.
According to the gcc maintainers this is a bug in glibc.
According to the glibc maintainers this is a bug in gcc.
blah rant rave curse slap stab blam, etc
Even though there's a hack to get it working, I'm staying with glibc 2.2 until both groups have stopped trying to break eachother's code.
But there's always PLAN B. And after three hours of compiling firefox 1.0, it turns out that the degradation curve since 0.8 has not changed course.
Some common sense inhibitor snaps in my skull and I ditch firefox. Alternatives:
Konqueror toy
Dillo incomplete
Links rules my console, but it has some
inherent disabilities
etcetcetc.
But there's always the "dead" Mozilla. It turns out that Mozilla is not as dead as commonly thought.
Mozilla has become much lighter nowadays. The e-mail, news and chat is seperated from the browser package now and doesn't swallow memory anymore and it's noticeably faster than before.
It can also use extensions, block popups and evil javascript code, and some other features we've started to like about Firefox. Among the differences are a more intuitive download manager and unfortunately the old text search. But the most important differences are its much greater stability and the fact that it is backwards compatible with glibc 2.2 and possibly even older versions.
So, contrary to the mainstream momentum, I've switched back to Mozilla. Getting it working took a few mouseclicks instead of a full compile and minutes instead of hours. I live happily ever after.
If you're having nervous breakdowns with firefox, consider this move.
Steven.