Running in the Browser
What I personally have hoped for was a VM in the browser that was addressable by a number of compilers creating bytecode. Everytime I see a platform that runs a VM underneath and doesn’t let you address that VM directly, I feel like a great opportunity has been missed. Oddly, MS’ CLR is the best example of a VM that lets you address it in virtually any language. They certainly didn’t invent the concept but they’ve promoted it. I think Sun did a major disservice to itself and VMs in general when they married Java the language, the Virtual Machine and the Religion into a single marketing entity. I mean who even knows that there are lots of languages that can be used to target the JVM?
A while ago I found a post by Brendan Eich talking about the future of the Mozilla VM and mentioned mono and the jvm as options. Yesterday, he posted about open web standards and I seized the opporunity to ask about bytecode addressability of JS2’s VM. His answer about legal issues is likely a big reason why mono was abandoned as an option:
“there won’t be a standard bytecode, on account of at least (a) too much patent encrustation and (b) overt differences in VM architectures. We might standardize binary AST syntax for ES4 in a later, smaller ECMA spec — I’m in favor.”
Of the three I initially liked the Morfik approach the best, but doing a bit more research, they seem to be well on the path of propagating the same patent issues that Brendan Eich attributes the lack of standard VMs to. Pity.
Looking forward to Rich Apps
So far, we’re stuck in the browser, and even with tabs, I sure hope this isn’t the future of applications. If we are to move beyond browser, what are our options?
Clearly, Adobe is leading the RIA platform wars with Flash and with Flex, SWF certainly looks more like a platform than an animation tool forced to render User Interfaces.
And Apollo certainly looks to push Flash as a platform as well as making it a stand-alone app platform. I certainly think this is going to be the juggernaut to beat. Given my dislike for the syntax of (Java|Ecma|Action)Script, it’s unlikely to be my platform of choice. And i don’t see a Adobe supporting cross-language compilation and support for Eclipse or Visual Studio at the expense of their Dev suite.
I really like the concept of WPF. It’s philosophy is what I want the future to look like. Mark-up and code separate, common runtime addressable in many languages on client and server, well developed communications framework. Ah, it warms my heart.
But, a) it’s closed, b) it’s only Windows (i’ll get to WPF/E in a sec) and c) boy, is it over-architected. Now, it’s at 1.0 release and if there’s anything about MS releases, they seldomly get it right in 1.0. We’ll see what 2.0 looks like.
WPF/E looks like a combination of simplifying WPF (is this 2.0?) and going after Adobe. And with Script# and recent admissions of some type of CLR on Mac for WPF/E, we’re looking at a trojan horse to get Rich Internnet Application Development in .NET established in both the browser and the desktop across platforms. Unfortunately, “across platforms” for MS still means Windows and Mac, while Adobe’s Flash 9 has demonstrated their dedication to encompass the linux sphere as well. I don’t think that’s going to change… I just don’t see MS going to linux with the CLR and I find the likelyhood of them leveraging mono‘s efforts just as unlikely. I wouldn’t mind being wrong.
This isn’t a platform per se, but I’ve seen a lot of cool tech demo’s using XUL and/or the canvas tag. Also looking at the work that Micheal Robertson’s AJAX13 has done, I think there are the makings of a stand-alone app platform here. If your runtime requirements are “install firefox, but you don’t even have to use it as your browser if you don’t want to”, that’s a pretty small barrier for a platform that runs everywhere. Personally, I hope someone straps mono or the recently liberated jvm to XUL and builds a platform out of it (you’d get mature WS communication for free with either), because of all the options that looks the most appealing to me personally.
There’s got to be more
Considering that GWT and Script# had eluded my radar up until today, I’m sure there’s even more options for RIA’s out there. I just hope that people developing platforms take the multi language lessons of the legacy platforms to heart. All the successful OS’s of the past offered developers many ways of getting things done. You looked at your task, picked the language that was the best fit to the task and your style of programming and you delivered your solution. VMs have shown that supporting many languages in an OS independent way is viable, so if you’re building a platform now, why would you choose to mandate a language and programming model. I sure hope that the reason for not going this route isn’t going to be “because the patent system is stopping me” — that would be the ultimate crime of a system that was supposed to foster innovation.