Link Details

Analysis of the problems Magnolia CMS 5.0 development team faced with ExtGWT and how the team decided to reconsider UI framework selection. Discusses how after lots of analysis, community interaction and development team vote, Vaadin was selected over the competition.

Posted by jl70368  |   Aug 12 2010 / 00:53

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.


User 85500 avatar

andrewm replied ago:

really interesting article looking at how things like the js translation approach of gwt/extgwt scale for larger number of modules, and why the server-centric approach of vaadin is sometimes a much better fit for an extensible system.

Reply 0 votes
User 14280 avatar

Joonas Lehtinen replied ago:

The 2nd part of the blog post also contains really interesting estimations on number of Ajax calls done by plain GWT vs. Vaadin. Great to see that they have actually analyzed some use-cases on that level in order to test their assumptions of UI responsiveness.

Reply 0 votes
User 762609 avatar

Alamoos replied ago:

Nice information. I always love X vs Y articles.

Reply 0 votes

Recommended Links

Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Play
  3. Akka
  4. Debugging JavaScript
  5. Design Patterns
  1. Apache Hadoop
  2. REST
  3. Java
  4. Git
  5. Java Performance
Connect with DZone