Twenty first century applets

I have filed the following thought under the heading 'total conjecture'.

Java-based browser applets were doomed from the start because browsers already had built-in virtual machines in the form of Javascript execution environments. It was only a matter of time until the native Javascript environment in browsers became powerful enough for rich application development. The collective wisdom of the market could see that fact. Consequently, selling the concept of a separate virtual machine 'stack' for client-side application development became a tough assignment.

This conjecture has caused me to revisit my conceptualization of an applet. Such revisitations are best commenced from first principles. Such as, what is an applet anyway? What makes an applet an applet?

An applet has two distinguishing features I would suggest. First, it lives on the network and is hauled down to your browser on-demand. It is not stored locally. Second, the application code is securely shackled so that it can only do network-shaped things. It cannot scribble on your hard disk for example the way 'thick client' applications can.

That description sure sounds like a modern day browser running a fancy Javascript-based application like gmail [1] doesn't it? As browsers have become bigger and better, the built-in Javascript programming language has evolved to the point where it has the sort of shackled ability to grab network data, draw screens and interact with the user that was once the domain of the Java applet virtual machine.

Posit for a moment, that this much is true. There is a snag in my nascent theory. An ugly little fact. Javascript is, for large application development, about as appealing as building a space shuttle with spaghetti. The nice thing about using Java for applets, it could be argued, is that the language is much better in ways that energize programmers and anaesthetize non-programmers.

Ok. Stick with me for one more little leap of logic here. Posit for a moment, that this much is true. What if, instead of writing the Javascript by hand, you continued to use your language(s)/tools of choice and they generate the Javascript for you? How bad would that be? Instead of generating so-called byte-code for a virtual machine such as the JVM, your programming languages could just generate Javascript.

Is that not a win-win? Happy programmers targeting a footprint that the user already has - namely their browser with no extra moving parts? No firewall funnies? No extra sandboxes to be separately verified? No new paradigms for end-users?

I have filed the following thought under the heading 'possibly interesting universal truth candidate':

Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world

• Email
• Print
• Share
  • Slashdot
  • Digg
  • Stumble
  • Reddit
  • Newsvine