Gwt why not

Has it changed? At the end of the day it is a meat grinder for churning out JS; not that it is a bad thing but not somewhere I want to put my effort. Many of these frameworks are chosen due to lack of technology X knowledge or something thereof I am very knowledgeable in JS, wrote some pretty serious stuff there, however I am now running a very time-critical project and I cannot afford to have junior staff waste time because of errors induced by context-switching from say Java to JS.

So please, if you have some real world example of why GWT did not work for you, then please describe it, otherwise let's not waste each other's time with hypothetical and highly subjective-colored discussions. Show 6 more comments. Active Oldest Votes. Union of problems, intersection of benefits Any languages is going to have it's own set of problems and benefits.

Separation of concerns We all know that as the size of a project grows, having good separation of concerns is critical.

In conclusion Improve this answer. Nicole Nicole I recognised some of the reasons we chose Wicket over GWT, hats off to the presentation.

And I haven't encountered a single one of these "problems" thus the FUD comment. If you know what you are doing it is wonderful, if you don't want to consider there might be a new better way of doing things then follow this "answer" and ignore this comment. Jarrod These are not "problems" to encounter, but plain descriptions of the nature of GWT. Where relevant, I further qualified them as being negatives specifically within the lens of our project's goals. If you have an alternate experience feel free to write it up.

Until then, the only unproven information is your claim that GWT is "new and better". By the way - since I wrote this answer, the company I no longer work for threw out over a year of several engineers' work, and rewrote the project without GWT. In less time. JarrodRoberson I agree with NickC, would be great to read an equally detailed write-up of your experiences. NickC "In less time" for rewriting a project doesn't count as a huge blow to GWT IMO; any project where you're basically repeating what has been done before even in a different framework or language ought to take "less time".

Show 3 more comments. Our requirements have been: client side UI layer to minimize server load browser compatibility web based RIA Easy performance optimizations No client plugins installation necessary, should work with a plain windows installation We choosed GWT and I never regret it.

What you get of the box is: browser compatibility Java based development process and code reuse easy minimizing of requests image bundle, ChrLipp ChrLipp 3 3 silver badges 6 6 bronze badges.

Add a comment. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta. Now live: A fully responsive profile. In the short term applications created in GWT and ARIA based are likely to face obstacles in functional accessibility due to support by the user agents that are in place within an organization, the assistive technology and version being used, as well as the complexity of creating widgets that must support all accessibility aspects, visual and programmatic focus, identity, state, role, events, keyboard access, visual appearance, and so on.

These challenges will be dimished over time as ARIA support increases and newer user agents become standard with organizations including the US Government. Search Field Search. Blog Posts. We use cookies to make interactions with our websites and services easy and meaningful, to better understand our web traffic, and to tailor advertising.

By continuing to use this site you are giving us your consent to do this. Cookies Close Cookie Notification. Close Privacy Overview This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website.

These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. Connect and share knowledge within a single location that is structured and easy to search. I'm considering use of GWT on a major in-house web app development project, namely it's major advantage in my eyes is the cross-compilation to Javascript which would at least theoretically help my team reduce the size of tech stack by one.

However, having been burnt before like most devs , I would like to hear from programmers who did actually use it on any problems with GWT which would hamper, or limit, it's use within a certain problem domain. I didn't read all the comments in the link that Jamshid provided, so this might have been addressed there If you want to build something closer to a traditional web app i.

However, if you want to build something with a richer interface that's more like a desktop app i. That said, GWT isn't perfect. Trying to integrate with third-party Javascript libraries is hardly pain free, and getting it to work how I wanted with maven and eclipse gave me a few headaches.

Ive been using GWT since As any technology, it has its pro and cons. Main benefit, by far, is the fact that if you have a team with strong java skills even maybe developers that worked with Swing then GWT is a smooth step. It will be more familiar and probably you will get things done faster at first with it in comparisson with other technologies. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. When not to use Google Web Toolkit? Ask Question. Asked 10 years, 10 months ago. Active 7 years, 3 months ago.