Gah! Again! People not explaining what something is on the landing page!<p>> GWT is used by many products at Google, including Google AdWords and Google Wallet. It's open source, completely free, and used by thousands of enthusiastic developers around the world.<p>Any amount of things fit that description. Beer? Air? Clicking "Learn about GWT" gets you this:<p>> GWT is a development toolkit for building and optimizing complex browser-based applications.<p>That's all it takes! Can we <i>please</i> start seeing these kinds of descriptions on landing pages. You're not selling a clothing brand, you are selling a toolkit to developers: I care first and foremost what the thing does, not how fashionable it is.
Grammar question from this non-native English speaker: does it sound right to say "you can quickly develop <i>performance AJAX applications</i>"? Wouldn't you say something like "high-performance AJAX applications" or "highly performant AJAX applications" (or just "performant AJAX applications")? It seems to be missing something.
Been using GWT for almost a decade. It makes it easy to develop and maintain enormous and complex web applications, which would otherwise be difficult if you had to rely only on JavaScript (both the language and the toolchain).<p>Being able to write the entire application, from the client and the domain model on down to the backend, in the same language, re-using classes across the entire application,
is a big advantage.<p>In addition, being a very mature toolkit by now, GWT has A LOT of features to make life easier. Transparent RPC/serialization, code obfuscation/deobfuscation, IDE integrated debugging, i18n, resource bundling, code splitting, JavaScript interoperability, and a lot of other stuff.<p>Current project: Real-time multiplayer GTA-style game based on HTML5 canvas:<p><a href="http://www.webworks.dk/html5engine" rel="nofollow">http://www.webworks.dk/html5engine</a>
I've never used GWT, but it looks a lot like ASP.NET (all the button declarations in code, heavy page lifecycle in code, etc.). Can anyone with ASP.NET knowledge comment on that? ASP.NET has many problems, there are valid reasons why most developers are moving towards ASP.NET MVC so I wonder what is the place for GWT in modern web dev.
GWT
pronounced «gwit»<p>Seriously? First I've heard this is how you pronounce it. And how does one pronounce gwit? I think I'll continue to call it: G.W.T.
I'm looking for a toolbox that can give me:<p>1. client-side (javascript) database access<p>2. automatic updates to the client's view of the database<p>And also:<p>3. automatic optimal re-execution of javascript code whenever something changes in the input (e.g., the database). Note the word "optimal", e.g., no glitches, and no (or minimal) unnecessary work done.<p>Of course, it should be fast :) Does anybody know where to find such a toolbox, or libraries that allow me to accomplish the above? Any pointers are greatly appreciated!
This <a href="http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsCompatibility.html" rel="nofollow">http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsCom...</a> seems to indicate that GWT still supports only Java 1.5. Is this true or simply outdated documentation?
It makes sense in the enterprise world where everyone love Java and Eclipse (at least as far as I can see). It doesn't make sense on HN, not at all.
Seems to me the textbook example of Java people trying to make everything Java (and failing at it, as usual)<p>While it's funny (and sometimes silly) to see a huge amount of .js libraries popping up, they're not adding a big block between the programmer and the browser.<p>And js may have its quirks, but it's <i>not java</i> and I'm thankful for that. I'd rather use js over java anyday, unless there's something really dependent on it.