Link Details

Link 465589 thumbnail
User 14280 avatar

By jl70368
Published: Aug 12 2010 / 00:53

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.
  • 38
  • 0
  • 17624
  • 2806
User 85500 avatar

andrewm replied ago:

0 votes Vote down Vote up Reply

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.

User 14280 avatar

Joonas Lehtinen replied ago:

0 votes Vote down Vote up Reply

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.

User 762609 avatar

Alamoos replied ago:

0 votes Vote down Vote up Reply

Nice information. I always love X vs Y articles.

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.

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java