I was forced to use GWT back in january this year (as a consultant you often do have to use a specific tool "just because") and it's been somewhat of a bumpy ride; at first I hated it with a passion, then I started to appreciate the strengths it does provide.
-- Losing devmode was/is a huge blow, but even more so is the difficulty in being able to just re-use webcomponents (such as polymer and others) out of the box without spending days writing overlays and wrappers. I believe this is also an area they are focusing on now, with improved js interop and perhaps a more lightweight widget system (?) I don't know.
But I do know that I would prefer to create UI elements in JS, neatly packaged and reusable like polymer webcomponents, while keeping all "business logic" to java code where it's just so much easier to ensure you are doing performing the right things on the right data - and like all JS, Angular apps also quickly become unreadable and unmaintainable over a given size - much quicker than any java app.
It's certainly a worry that it's hard to find any roadmap with dates for the future of GWT and that google doesn't seem so interested in it anymore, so less resources available to work on it and the learning curve for new people to contribute is pretty steep.
Does GWT have a future? I hope so, but I'm by no means certain. Seemless interop with webcomponents is the key, IMHO.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment