|
|
|
|
|
|
by kls
5775 days ago
|
|
|
just to be clear, this is all relative? Lets face it, in the world of creativity and development, there is no right and wrong. I have seen some beautiful applications developed in VB, a technology I despise, I am also continual impressed with what the PHP guys produce, despite the fact that I personally loath working in PHP. So in that context GWT is not right for me, and I find that it is not right for a lot of other development houses, because they are focused on design centric concerns as much as development centric. Yes, you can find a master of both worlds, but many times you can find a wonderful designer who's logic escapes him, and we have all seen the horrors of a programmer designing interfaces. It has been my experience that it is easier to find masters of one and mediocrity of both. So for me, and my development efforts separation of concerns is the right thing. For others GWT may be the right selection. I just wanted to be clear in my statement, I am not telling anyone what is right for them, I am telling them what is right for me and the developers I work with. |
|
|
Everyone has their preferred toolsets and frameworks and of course they should use what they feel is most effective. Case in point: my shop uses very little GWT - my coworkers prefer different tools (and often so do I; GWT is overkill IMHO unless you're building something big).
But this is all not really relevant to my point:
I was talking more about how the linked-to blog post was kind of web-development-101 stuff that everyone already knows and somehow, sadly, still received many upvotes/comments. I only brought GWT into the mix because some guy wrote a blog post about listening for URL hash changes and is presenting it as the future of web development, while (using GWT as an example) people with PhDs have written an optimizing Java to Javascript compiler and engineered very good solutions to difficult client-side web development problems that completely trivialize something as basic as hash change history tokens.