Web as the Platform – Day 1 at the Ajax Experience
The next Web Revolution is on its way
Ben Galbraith gave the keynote speech this morning to open a conference that discusses different topics around Ajax and what is believed to be the next revolution in the web. ECMAScript5 brings several big changes and opens up new opportunities. Besides ECMAScript5 there are many existing technologies that already open several doors for the next Application Revolution:
- Canvas: Enables a richer user experience in the browser bringing web applications closer to native applications. Check out some of the stuff at http://ajax.org (click on 3D charts)
- Web Workers: In case you miss background threads – Web Workers bring back the ability to process work in the background – decoupled from the main UI thread. Having the ability to outsource work to a different thread will avoid unresponsive web pages and improves the overall end user satisfaction. Over are the times where web applications stuck – users hitting the refresh button or restarted the browser in the hope of solving an unresponsive application.
- Desktop Integrations: Appcelerator provides the ability to take web technology to the desktop or to your mobile device. Write once – run everywhere – a promise that we have heard many times. There are other technologies out there that enable Web to be the next Platform technology. Besides Appcelarator we find Fluid, Mozilla Prism, Adobe AIR, Google Gears or PhoneGap that bring web technology on any device – running it like a native application.
Higher expectations on web performance
How do you address the next web revolution?
Some believe the next revolution is already here – some believe that the next HTML standard will bring it. What is your take on it? Are you playing with new technologies? What are the good and the bad things you have seen?
My recent feedback with our customers showed that similar problems that we address on serverside application performance issues also apply to the new browser world. Frameworks that are not used correctly lead to performance problems. Too many network roundtrips to the server, blocked UI threads or too many unnecessary object allocations lead to bad end user experience. Moving back to the client (browser) might not be a bad thing – but - assuming that we get better overall performance by leveraging the client resources is just an assumption. It has to be done right in order to revolutionize the web again.