SoylentNews is people
SoylentNews
Submitted via IRC for Sulla
When Georgia Bowen was born by emergency cesarean on May 18, she took a breath, threw her arms in the air, cried twice, and went into cardiac arrest. The baby had had a heart attack, most likely while she was still in the womb. Her heart was profoundly damaged; a large portion of the muscle was dead, or nearly so, leading to the cardiac arrest.
Doctors kept her alive with a cumbersome machine that did the work of her heart and lungs. The physicians moved her from Massachusetts General Hospital, where she was born, to Boston Children's Hospital and decided to try an experimental procedure that had never before been attempted in a human following a heart attack.
They would take 1 billion mitochondria — the energy factories found in every cell in the body — from a small plug of Georgia's healthy abdominal muscle and infuse them into the injured muscle of her heart.
Mitochondria are tiny organelles that fuel the operation of the cell, and they are among the first parts of the cell to die when it is deprived of oxygen-rich blood. Once they are lost, the cell itself dies.
But a series of experiments has found that fresh mitochondria can revive flagging cells and enable them to quickly recover. In animal studies at Boston Children's Hospital and elsewhere, mitochondrial transplants revived heart muscle that was stunned from a heart attack but not yet dead, and revived injured lungs and kidneys.
[...] In the only human tests, mitochondrial transplants appear to revive and restore heart muscle in infants that was injured in operations to repair congenital heart defects.
Source: https://www.nytimes.com/2018/07/10/health/mitochondria-transplant-heart-attack.html (alt)
(Score: 2) by jelizondo on Thursday July 12 2018, @12:49AM (3 children)
Jesus H. Christ!
I tried IPX/SPX over an international leased line and had all sorts of trouble; talked to some guy at Novell and voilá, they sent a patch that allowed the connection to kind of work. It was slow as hell but we could transmit enough data to make it, but no more than that.
Of course, IPX/SPX was much better than anything else out there in a local network, just wasn´t designed for wide area applications. I hated (hate?) Eric Schmidt for killing Netware with (IMHO) so many false starts.
Anywy, get off my lawn you dirty children!
(Score: 2) by RS3 on Thursday July 12 2018, @03:44AM (2 children)
I know we're off topic, but I can't help myself.
Actually IPX was designed to work well in a WAN, you just have to use routers that correctly handle IPX. IPX has 32 bits of network address, like IPv4, and 48 bits of "node number", or device address, which was usually the MAC address but didn't have to be. So you see, IPX could handle way more addresses than IPv4. Then it has 2 bytes of "socket number" - same as IP.
By "international leased line", I'm guessing some kind of T1, X.25, frame relay, ?? As to slowness, you can't blame Novell / IPX - my guess is that the leased line couldn't handle IPX properly or at all, and maybe you were using IP tunneling?
(Score: 2) by jelizondo on Thursday July 12 2018, @05:43AM (1 child)
Oh God! This was in the early 90's, can't quite remember but probably 91 or 92, maybe even 89. The leased line was just that, a line where we could get four voice channels or two voice channels and a data link, 128 Kbps if I remember right.
Anyway the problem was a timeout because of the slow line, which was made a configurable parameter in the patch I got.
The guy who sold me on Netware was so sure, that he gave me a written "your-money-back" guarantee. We were using HP 832 minicomputers (HP-UX) at the time and I was not very comfortable switching, but he said he would refund the money. I never gave the letter to my boss, if it didn't work it was a "cover your ass" letter, but I could not let my boss know I had doubts, otherwise he would have never approved the project.
In the end, I fell in love with Netware and hated having to move to NT, forced by other people (mostly the CFO) and Schmidt's bungling Netware.
I will always miss the simplicity and strength of Netware; after so many years, everything seems so much more complicated and prone to failure. Maybe some engineers decided on job-insurance and created the mess we have today.
(Score: 2) by RS3 on Thursday July 12 2018, @08:54AM
I can't speak about other engineers because I don't know, but it was the exact mess you described- non-technical managers making "business decisions", buying into MS, NT, etc., and killing off Novell, that opened my eyes to the problem. To this day I don't see a solution to the problem of us engineers being forced to use a technology we would not choose if given the option.
Yeah, the timeout problem is an interesting issue in communication protocol theory. WANs are a good thing, as we all know, and long timeouts are to be anticipated. I'm glad they gave you that patch, but I feel it should have been configurable from the start.