I wouldn't be so quick to hop on the chromeOS bandwagon. It may not be suited for a user like you just yet (or me for that matter). That and the specs of the current crop are disappointing to say the least. Good thing is, chrome will do for now.

However, I can see the huge potential in the platform and the momentum that it's generating. I'm hoping to be able to use a platform like this in the future with the web and my own personal server.

ECMAScript (also known as Javascript) has a VERY significant feature in the pipe for ECMAScript 5. Object extensibility control!
http://ejohn.org/blog/ecmascript-5-o...nd-properties/

This basically means that the developer of an object can mark the object as non-extensible, preventing future property access.

Why is this @#%*ing cool? Because it allows Javascipt Just-In-Time (JIT) compilers to safely forego the test of an object's property existence upon calling it! Currently Chrome's V8 does this in 3 assembly instructions using hidden-classes representing the latest state of an object -- but this is no longer required for these objects. This equates to code that is potentially static in nature, seamlessly interwoven with dynamic code, and compiles that will approach the speed of native code. Add in a little post-compilation optimization (runtime profiling, inlining, additional optimizations/crankshaft on hot traces, etc) and you get code that is potentially BEYOND the speed of natively compiled code, which can't see code behaviour at runtime (only compile time).

This type of flag wouldn't be useful for all objects, but certainly is useful for those that require additional security and/or are performance sensitive (think a game inner-loop).

It also offers finer control over properties, such as writeability, enumerability, and configurability. FTA:

• Writable. If false, the value of the property can not be changed.
• Configurable. If false, any attempts to delete the property or change its attributes (Writable, Configurable, or Enumerable) will fail.
• Enumerable. If true, the property will be iterated over when a user does for (var prop in obj){} (or similar).

These are incredibly powerful features that will transform javascript.

Currently Chrome's V8 has impressive ECMAScript 5 support.
http://kangax.github.com/es5-compat-table/

Man, I love javascript as a language. It has slowly edged out C as my fav language of all time. It is the right mix of simplicity, and elegance and mixes functional programming with a model that allows it to easily emulate many programming patterns.

What's not to love?!

Here's a BIIIG one: QUAKE in the browser via NaCl!
GAME LINK: http://nacl-quake.appspot.com/

As always, Zero-install, Zero-configuration! Play the game right now in your browser in as little as a single click! This is the full game.

This is INCREDIBLE. It runs at perfect speed (ultra smooth) despite being 100% software render! The only problem (and this is a pretty major one) is that the controls via mouse need work: if the mouse tracks out of the window, then the game looses access to the pointer. A game like this (being controlled by the mouse) needs to be run at full screen.

In any event, it is a fantastic demo of NaCl, and the first of many ports, I'm sure!

Get the latest Chrome Beta to enjoy!