This post originated from an RSS feed registered with Java Buzz
by Marc Logemann.
Original Post: Why java developers fear Ext JS
Feed Title: Logemann Blog
Feed URL: http://feeds.feedburner.com/LogemannBlog
Feed Description: Marc Logemann's thoughts on java and other stuff
When we speak of beautiful widget libraries, we should not mention any java based framework like wicket or MyFaces or something. They all mainly concentrate on supplying a good web framework and offer some components to use but we dont get much help when it comes to building nice forms for example.
On the other side of the river we have javascript frameworks like Ext JS. When you look at their sample pages, you are just blown away how nice all this looks. Look at the form example for instance. Its just nice. But the love story of Ext JS ends very soon when java developers will check the source for the example, like the one for the form. In case of wicket or JSF, its impossible to combine those technologies elegantly with Ext JS. The idiom that a form field directly corresponds to a pojo attribute is not working anymore. Instead you end up writing JSON communication classes and do a lot of stuff which comes for free with major java web frameworks.
I bet as soon as you start using Ext JS, sooner or later you will throw away your java IDE debugger because you dont need it anymore and start being active comitter to Firebug because this is the main tool you are using sooner or later. No matter how cool those hughe JS libraries are, i will not give up my architectural principles and my focus on maintainability.
Previous Topic
