|Speed||fast – 4 to 8 xJS||slower – 1/4 to 1/8 Java|
|No.of GUI Components||many||many|
|Visual Design GUI||Very Good||Just okay|
|Database Support||Excellent||Improving with AJAX|
|Cross OS Platforms||Excellent||Very Good|
|Web Frameworks||poor with JSP, JSF||poor with std JS|
|Web Frameworks II||good: applets+XML||good withAJAX|
Now this comparison is ballpark and will be followed up in the regular OpenSourcery with more detailed evidence. But it is i nteresting to note two other major trends. First, AJAX is the hot item in the market right now with Google, Flickr and many others doing nifty SaaS websites and services that Java developers using the JSP and JSF paradigms will be hard pressed to match. But they can by just emitting appropriate AJAX code in their JSP/JSF routines. Pure Java developers who use applets like Droplets and others already can deliver good response time and will have to look at local XML databases for offline temporay files (but compressed and encrypted to secure privacy and critically secure data).
However a good trend is that there is already some so-operation among AJAX developers and frameworks with both Java tools and among themselves. But there has been a proliferation of frameworks and AJAX part tools so the failure of Dreamweaver/GoLive to establish a common development framework has hurt. Some would point to Microsoft and Atlas; but we have major problems there.
We are rejecting Microsoft AJAX tools on 4 grounds:
1)Bill Gates “Mea Culpa” fell way short of the mark;
c – and most importantly when MS adds a stick to standards switch in all its Web development tools
then we will consider Bills “mea culps sincere and Microsoft Web development tools worthy of some consideration.
2)the current tools use many proprietary techniques both on the client and server side – so that Atlas/AJAX code will not work on Linux, Mac, Solaris and other OS systems. It is the old proprietary trap revisited yet again.
3)MS says that the Atlas/AJAX code works with
4)Microsoft used to say “when numbers warrant we will develop for that platform and applications. LAMP currently has 65% of Web servers even with a 6% dip in January with a crass move to get parked and otherwise unused websites into the Windows fold. Microsoft realy has to open its devlopment beyod Web Service and XML only interoperability.
So our advice to developers is to stay away from MS Atlas/AJAX because the code set is proprietary, will be changing dramatically with the move to Vista and WinFS with disastrous VB-like help for your transition, and it becomes essentially stand alone code. Also ISV developers have to be very careful of Microsoft – Redmond may eat your hard won market share out from under you – a la OS utilities, BI, game, project tools, Business apps and a whole litany of other Windows application vendors.
Summary of this Argument