We already know the -idea- works - cooling the body down extends the amount of working time on the table.

It will be interesting if this technique works as they expect. I'd think the hardest part is keeping the blood viable once "replaced" and not causing problems during the swap due to chemistry changes (eg different/reduced energy/waste/oxygen exchange)

Do the swap fast enough and that's not a problem - but try to do it too quickly and you're going to cause a lot of damage.

Meanwhile, in reality, the administrators I know have to do more work than three of us and are held up to a higher standard. Better not make a mistake, or you're career is over!

So A is better than B, if you ignore the crippled engine problems? Good sell!

Just what we need... airborne radioactive ash!

That's not all that much. 10x10 would be 100...

Interesting how KDE and those responsible for Unity have differing perspectives... who would have thought?

I couldn't even figure out how to bring up a menu on that piece of shit. I had to use the task manager to quit, try (and fail) to find any useful documentation, and cancel my account.

Approximation != guessing.

We all love to hate when that happens!

Calculus is not mimicry.

What's not calculus about that? You approximate the result and further refine it with additional data/time. With even more practice, you certainly CAN see where it's going to land (barring interference by another force, such as wind).

We are quite good at this. How do you think things like hitting moving targets with arrows happens?

So, the fly has a biological PID controller?

... which is never.

EL5 is, while supported, getting a bit old. Hell, EL7 is just around the corner!

You clearly don't understand the lifecycle of a production OS.