IBM's EGL, http://www-949.ibm.com/software/rational/cafe/community/egl, is meant to make building Web 2.0 apps a lot more easy. Looks interesting. Basically you program in the EGL language and they generate Web 2.0 pages for you and you can debug it without having a server. I don't develop in Java or use Eclipse really so I probably won't touch this one, but still interesting.

Microsoft has released Doloto, http://research.microsoft.com/apps/pubs/default.aspx?id=70518, that from what I can tell just pushes the JavaScript you need as you need it. Can I coin the term Javascript on Demand (JoD) or has someone already claimed this? :) Doloto profiles your application and then it figures out which JavaScript you need and makes stubs for functions that are not required right away and groups functions into groups that are downloaded together called clusters. So, once once it's profiled your app, the new JavaScript can be uploaded to your server to improve performance.

According to, Somasegar's WebLog, http://blogs.msdn.com/somasegar/archive/2009/09/04/doloto-on-devlabs.aspx, "In our experiments across a number of AJAX applications and network conditions, Doloto reduced the amount of initial downloaded JavaScript code by over 40%, resulting in startup often faster by 30-40%, depending on network conditions."

I'm just wondering how this works with dynamic pages and 3rd party components that have their own JavaScript. I understand what they're doing, but how do you get 3rd party components to not send the original JavaScript to the client as well that shipped with the component because a lot of times these are embedded resources.

Thoughts anyone?

Labels: AJAX, doloto, EGL, javascript, RIA