Project Bespin and the Future of Web UI According to Google

DZone 's Guide to

Project Bespin and the Future of Web UI According to Google

· Java Zone ·
Free Resource

Last week, Mozilla Labs unveiled yet another innovative project called Bespin. Bespin is an online code editor. I shared my opinion on Online IDEs in the past (here and here). They open new opportunities, yet, we are still far from the promised land. I don't see a great difference between Bespin and other attempts I encountered (Eclipse E4, Heruko, DevUnity). The idea is not new. Yet, there is something very interesting about project Bespin.

Project Bespin demonstrates the use of the Canvas HTML element. In a nutshell, this technique enables a completely free UI rendering. The code editor is rendered in JavaScript, not using traditional HTML tags. From the initial demo of Bespin, the UI looks very different than the UI one usually expects in Web applications. It is very responsive and very rich, much like a desktop application. It is innovative and not bound to the current browser paradigms (e.g. the auto-hiding scroll-bars).

This technology can be compared to Microsoft Silverlight and Adobe Flash/Flex. In fact, I see it as a clear contender. I noted in the past that Google considers JavaScript to be the future of web UIs (the Chrome browser is a proof) and this is just another brick in that wall. Well, we know that "Mozilla... is a charitable arm of Google" (from TechCrunch), so the connection is quite obvious. Google uses Bespin to show the developers community that the future of JavaScript-based web applications is bright. No need to switch to other technologies, we've got it all right here.

The Canvas approach has its' drawbacks. The main caveat is that it is not supported in Internet Explorer, thus, will not work for the majority of the web users. That's where Google comes to the rescue with the Explorer Canvas project which enables the Canvas tag in Internet Explorer. I didn't test Bespin on IE with that extension from obvious reasons (I use a Mac). Let's suppose that in a couple of months, Google comes up with a better GMail UI, based on HTML Canvas: the result would be either a mass migration from IE to other browsers or IE adding native Canvas support. If I had to take a guess, I would bet on the former. Microsoft is already losing the browser war. IE does not need more nails in its' coffin. 

So what can we expect next?  Probably a GWT implementation which renders the UI using an HTML Canvas rather than plain HTML, taking GWT to the next level in terms of UI richness. Imagine the power of Java with amazing UI capabilities (much nicer than current Java UI frameworks) and a thin-client deployment model. That's the holy grail right there! 

From http://blog.zvikico.com/


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}