My (limited understanding) is no.....but fewer of them "clog the pipe" and make it to the other end (lower resistance values).

I disagree with your coder lock-in statement. But I agree with your "throw a dart" metaphor.

Just because you CAN code an algorithm in a language doesn't mean it's the best option. Just because I can drive a screw into a 2x4 with the heel of my shoe doesn't mean I should.

Languages are developed to make certain problem domains easier. If they are flexible enough, people will adopt them for other problem domains as well. If they aren't flexible enough, they might stick around in their problem domain, but they'll stay on the outskirts. That's it.

Very true. For "the common man" to know what direction to take, too many choices can be bad......especially when there is more similarity than differences and not enough experience to know which differences will be important to them in the future.

But you should be able to cache the unchanging portions (the template as it were) and not cache the data leading to BETTER caching. If I'm using some sort of data-binding and AJAX, my HTML template page and the Javascript logic can both be cached. Then, my page can be dynamically (and constantly) updated with AJAX data. As the data changes, I don't have to keep sending an entirely new HTML page that only differs by some portion of the content.

All of the reasons that you like Java are the very same reasons that I opt to feed my family coding in the various .Net technologies (ASP.NET, C#, Javascript, HTML, etc.). Microsoft is very developer friendly (just as Balmer).....but seriously, Visual Studio is a great IDE.

But I firmly agree with the aspect of taking less money to do what you love; that's far more important than money. My worst day doing my current job is better than the best day at my previous job.

After Egypt might be a fun game.......sort of an RPG that reminds me of Wasteland......

My computer has a built in batter backup (it's a laptop). As long as my strip protects from the spikes, the actual outage is inconvenient more than anything else.

This is one of the reasons that I kill the Chrome task if I get anything even remotely fishy (phishy) looking popping up.

Turn around.....the congregation is over there. This is the choir. But preach on.

For those people, the experience on lower-end Windows Phone devices is usually better than the experience on lower-end Android devices......I suspect that's where MS will garner their greatest bump in marketshare.

An unlocked Lumia device for under $100 US ---- unsubsidized!!! And it's actually a decent phone for the money and doesn't suffer as much UI stutter as a knock-off Android device.

Does it ensure that your Stripper name is protected akin to a business license? That would be a useful benefit of registering.

I still have my copy as well, but I haven't fired it up in a while (emulators!).

But those Atari 2600 carts were pretty robust.....just ask any of the ones that were flung across my room. I would bet that a cart wrapped in cardboard survived rather well.

This. Languages that enforce their rules at compile time vs run time should inherently lead to higher quality code just by "accident". You can still write bad (or good) code in any language, but a language that lets you do whatever you want requires you to be much more rigorous in your testing strategy to ensure higher quality......and we all know how much developers love to test (and to document).

Can't we sick Greenpeace on PETA -- get two of most polarizing groups fighting each other? The camel wasn't injured (was probably well taken care of) and was more environmentally friendly than a Jeep.

Another feature that I would love to see in CSS is "relative to another element" via a selector.

.SecondContainer{
height: ||.SomeContainer||.height
}

That should make layout simpler.