If you read through his "rants" section of his website, you will see he's not a racist, he doesn't call black people "niggers", just people he doesn't like.
I'm not sure this is what he meant, but I think he refers to the temperature of the water. If you lower the pressure, it takes a lesser temperature to get the water to start boiling.
So if you go on a mountain and put a pot with water over a fire, it will start evaporating rapidly(boiling) at a lesser temperature than 100 degrees Celsius, so he needs a more efficient way to transfer more heat into the water to get it to 100 degrees Celsius(normal boiling temperature).
Opinion: nobody should be shipping any JS to oldIE, period.
Their JS engines are woeful. Even if you can get something app-like (the kind of thing you would use dart for) to work, your app won't scale w.r.t. perf so you're painting yourself into a corner.
Some do, of course, but some of the rest of us are more interested in future advantages. If you need to target legacy browsers, legacy technologies are widely available.
If you'd like the future to be as good as possible, you might want to build new tools without the same old constraints.
I personally built a single page application about 2 years ago that worked in IE8, thanks to jQuery and the ecosystem of the time. jQuery, jQuery UI, various plugins incl. jsTree & DataTables.
It flew in Chrome, Firefox and Opera, even then. In IE8 it was slow as hell. Event listeners were slow, ajax and parsing JSON was slow. Everything was crazy slow. The app felt lumpy and awful. And when I hit bugs, the developer tools just were not there.
I would never do this again.
I'd wager that for IE < 8, for any non-trivial app, round-tripping to the server will give you a better UX than using JavaScript.
On my old laptop, an HP G61 something, I had a Mobility 4200. I hadn't been able to test it with the released 3.11 (replaced it before it was out), but I did always add the patches from the drm-next branch that was developing all of this. It did make a decent change in the temperature of the whole laptop. From being about 60C down to about 40C if I remember right. At least when I wasn't trying to run minecraft.
I have an older 3xxx card as well and enabling DPM noticeably reduced work temperatures. I'd say the temperature levels with DPM enabled are similar to using fglrx propriety drivers.
I have tried and it helped a bit in that the fan doesn't seem like it will take off, but temperature wise not that much of a difference.
At least it's not shutting down, it's staying at around 66 degrees when idle.
My setup is also slightly more complicated because this laptop has hybrid graphics (basically 2 radeon cards), in this case turning off switcheroo helped a bit as well.
The lessons this laptop taught me:
- don't buy ATI/AMD
- don't buy hybrid/dual graphics
I'm very pleased with my other laptop with a Sandy Bridge CPU and integrated Intel grahics HD3000.
I'm sure I don't know most of them (e.g. I have no idea how Prolog does error handling), but I know of:
* the Haskell/ML statically typed approach, error possibility is type-encoded through an Option or Either type; even in cases where it is possible to implicitly ignore return values[0] the compiler will warn or error; the standard library provides high-level operations to pipeline results (build a pipeline of operations which will only transform non-erroneous results, and will let errorneous ones go through)
* the Erlang dynamically typed approach which makes use of tagged pattern matching to make value assertions trivial. It is not shorter than the Go version when fully handling things, but assertion can be used to fault processes during development or when in-process user-visible reporting is irrelevant (fairly common in erlang) yet remain easy to find and replace with more involved handling if needs be
[0] because haskell strives for purity, ignoring return values in non-monadic code makes very little sense and I'm not sure it's possible at all short of unsafe* functions. It is possible in monadic code (e.g. do blocks)
