Molten salt has a lot of advantages as a working fluid over water, unfortunately the major big disadvantage outweighs all the positives.

Viz. the conditions inside these reactors would be absurdly corrosive. F salts are chemically aggressive, and that aggressive increases with temperature. That is compounded by the fact that the reactor materials will also be bombarded with significant neutron fluxes, and by the presence of all dissolved decay products in the working fluid.

We simply don't have materials that can stand up for any length of time to that kind of abuse.

You see these articles over and over again, because the non-profit industrial complex doesn't like the Gates Foundation. They resent the fact that the foundation doesn't pay sufficient obeisance to complex's people, myths and way of operating. They especially hate that the Gates Foundation doesn't have to fund-raise which most people in that sector simultaneously think is beneath them and spend most of their time doing.

You aren't sending a message. You are negotiating keys for a symmetric cipher over which you will send a message. So Alice and Bob can (and should) each select a resister at random until they collect enough undetected and non-colliding bits.

I think craps with large enough allowed odds bets (e.g. 100-1) beats perfectly played non-card counting blackjack.

The aftermarket widgets are great, but the core translation engine, dev mode and RPC have (almost) no one working on it except google engineers - and there are many fewer of them today than there were two years ago.

That's a problem.

There is an argument (a bad one, but an argument) to be made for significant white space. There is no possible rationale for javascripts' usually-insignificant-but-occasionally-very-significant white space gotcha.

GWT is great, but unfortunately the team at google has a) been decimated in favor of dart and b) in any event has/had a really short attention span.*

The project is nominally open source but AFAIK all the committers are google.com. The eclipse development mode is increasingly buggy as attention is diverted to the new source map method of debugging they are cooking up. Plugins for Firefox come out just in time for the next release.

As much as I love the concept and much of the implementation, I don't know that I wan't to risk devoting to much more resume space to a technology that may be a dead end.

*Seriously - read the release notes for the dot releases since 1.6. Every version there is a completely new preferred way of doing things. Bugs filed against anything but the latest and greatest paradigm languish forever.

Right, a language with a function named mysql_real_escape_string() is just different. As is a language with occassionally significant whitespace.

Perhaps the word you were looking for is 'special'?

It is a somewhat jargon-y term used by compiler programmers to refer to pulling functions or values up into a wider scope. Often this means that the compiler can optimize away many duplicates of the same function or value.

Turbocharger are rightly unpopular because of turbo-lag. If I step on the gas I want to accelerate now, not five seconds from now.

Also they are exposed to harsh conditions and so tend to break before other parts.

The geek culture guy?
God he was annoying.

This post is timely, but omits the information that makes it timely.

The King Center just announced a few days ago that it plans on launching a website with comprehensive digital access to the written and audio-visual archival materials it controls.

http://www.marketwatch.com/story/jpmorgan-chase-co-and-the-king-center-announce-the-king-center-imaging-project-an-unprecedented-joint-digitization-initiative-2011-08-25?reflink=MW_news_stmp

Have you ever actually walked along the Hudson at the bottom of the Palisades? That 'hiking' trail is more like a garbage dump. Typical NJ.

The correct nomenclature is "on the gripping hand".

Turn in your geek card on your way out.

You do realize that you are posting on a website that: a) made its founders a fair chunk of change and b) was first implemented as a disastrous mess of perl spaghetti code.