By jl70368
via philipp-baerfuss-magnolia.blogspot.com
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.
-
Useful Commands to Deal with SVN
-
Bougex
-
NoSQL, Graph Database for Enterprises – How to derive Logical Graph Domain Data Model from Logical Domain Data Model?
-
A Tutorial on Primary Index in Teradata
-
Comparing 3rd party Windows Phone Control Sets
-
How to use namespace in struts to separate web application modules
Comments
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.
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.
Alamoos replied ago:
Nice information. I always love X vs Y articles.
Voters For This Link (37)
Voters Against This Link (0)