In conversations with Michael about the hype of enhanced JavaScript performance via V8 in Chrome, he ridiculed the intent of making JavaScript do what Java was supposed to do. This directly stemmed from the comment that V8 compiles the JavaScript into machine code rather than continually interpreting it.
Sure, Java has an intended place with an intended prerogative - write once run anywhere. So if Java did so well, why was there ever room for Flash? This isn't a debate of technical superiority and appropriate application of tools. That debate ended around 2000 and was cemented by 2005 and is now a dead horse. Java in the browser is dead - get over it.
So why the grief over JavaScript being the language of choice? Is it ideal? Technically no, but realistically yes. Why? Simple: given that a web developer has appropriately written their code, and adapted for the inconsistencies between the different browsers, their site will work out of the box for the vast majority of client machines without installing the newest version of Flash or the latest Java VM.
Ok great - you have a platform that is hodge-podge across the board and mimicks alot of things that have been done in the past better, why should anyone munch down this rewarmed left-over?
JavaScript's ubiquity is the answer. Mashups is the answer. The future application platform is the answer.
Read on in future installments, gotta go for now.
