Hi,
I think future of GWT being threatened by 2 evil:
1. Big compile time (specially when size of module increase) which increase development time, and usually in compile time, developer will concentrates on subjects other than development (!) and it takes a few minutes to concentrates on development again.
2. Complex and excessive code.
For example, I used Spring Roo to generate code for an entity with 4 field (property or relation) based on GWT, Spring & Hibernate. It generates about 1600 line code just for CRUD (create-read-update-delete and search) operations (!). Spring Roo generated GWT code based on MVP and Activity&Places, UIBinder,...
Recently I designed a code generator based on GWT, Spring and Hibnerate. It generates about 700 line code for same entity, same operations and same functionality (but I don't use MVP, Places&Activities or RequestFactory). So it is possible to decrease complexity and size of code.
MVC pattern (predecessor of MVP) which introduced in 1990s by GoV (Buschmann et. al.) as an architectural pattern, but it was not used widely and now simpler versions of it are used. It shows that a complex pattern will not survives even it designed based on best OO principles.
MVP is a good pattern but if you used it, you should accept its complexity, So use it when is necessary. (there is no such thing as a free launch!)
On Mon, Sep 26, 2011 at 3:42 AM, Gal Dolber <gal.dolber@gmail.com> wrote:
-- I think future of GWT being threatened by 2 evil:
1. Big compile time (specially when size of module increase) which increase development time, and usually in compile time, developer will concentrates on subjects other than development (!) and it takes a few minutes to concentrates on development again.
2. Complex and excessive code.
For example, I used Spring Roo to generate code for an entity with 4 field (property or relation) based on GWT, Spring & Hibernate. It generates about 1600 line code just for CRUD (create-read-update-delete and search) operations (!). Spring Roo generated GWT code based on MVP and Activity&Places, UIBinder,...
Recently I designed a code generator based on GWT, Spring and Hibnerate. It generates about 700 line code for same entity, same operations and same functionality (but I don't use MVP, Places&Activities or RequestFactory). So it is possible to decrease complexity and size of code.
MVC pattern (predecessor of MVP) which introduced in 1990s by GoV (Buschmann et. al.) as an architectural pattern, but it was not used widely and now simpler versions of it are used. It shows that a complex pattern will not survives even it designed based on best OO principles.
MVP is a good pattern but if you used it, you should accept its complexity, So use it when is necessary. (there is no such thing as a free launch!)
On Mon, Sep 26, 2011 at 3:42 AM, Gal Dolber <gal.dolber@gmail.com> wrote:
I also agree, but I don't think google is responsable for improving the user framework on gwt.It is great that they put together uibinder, gwt-rpc, the editors framework and other goodies, but its your choice to use them or not.I am personally happy with a strong gwt core, and that just keep getting better with each release.--On Sun, Sep 25, 2011 at 8:32 PM, camerojo <jadcpub-google@yahoo.com.au> wrote:
I also agree - I hope the Google folk look at this.
GWT is a wonderful concept, and we should all be very grateful for it,
but some of the implementation is certainly over engineered.
In particular I wish that more focus was given to fixing basic bugs
(of which there are quite a few) rather than coming up with new high
level architectural concepts.
Of course all developers would prefer to be playing around with new
concepts rather than fixing bugs in existing code, but production
software demands that basic debugging must always take priority.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Guit: Elegant, beautiful, modular and *production ready* gwt applications.
http://code.google.com/p/guit/
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment