Live data from Hacker News

GWT 2.0: So good it's ridiculous

timepedia.blogspot.com

1–10 of 48 posts

Re: GWT 2.0: So good it's ridiculous

#3

How could trading the expressiveness of JS for the expressiveness of Java without the commensurate increase in performance be "So good it's ridiculous".

You clearly didn't RTFA.

I'll give you my personal reasons for liking GWT in a few short bullets.

1. Better tooling - IDE refactoring when I need to change things. Red squigglies when I make a typo or reference something thats not there. A real debugger with breakpoints for finding bugs. Auto completion and auto style formatting so I dont have to type so goddamn much.

2. Compiler optimizations - Your code gets faster and smaller. Write maintainable code, have it turned into performant code.

3. API's and libraries - easy client server RPC, discoverable wrappers for the DOM APIs. Reuseable widgets that have predictable structure/side effects!

4. Maintainable code base - If you worked with more than 4 engineers on a non-trivial product, you would understand the appeal of a Java code base. UIBinder lets me not worry about CSS name collisions.

I would go on, but you seem like a TLDR type of person, so it would probably be a waste of my time.

Re: GWT 2.0: So good it's ridiculous

#4

How could trading the expressiveness of JS for the expressiveness of Java without the commensurate increase in performance be "So good it's ridiculous".

The performance that GWT is able to get is impressive. There are all kinds of optimizations they can make because of the assumptions they have, especially that you will run the code through the compiler.

Re: GWT 2.0: So good it's ridiculous

#6

How could trading the expressiveness of JS for the expressiveness of Java without the commensurate increase in performance be "So good it's ridiculous".

You clearly didn't RTFA. I'll give you my personal reasons for liking GWT in a few short bullets. 1. Better tooling - IDE refactoring when I need to change things. Red squigglies when I make a typo or reference something thats not there. A real debugger with breakpoints for finding bugs. Auto completion and auto style formatting so I dont have to type so goddamn much. 2. Compiler optimizations - Your code gets faster…

Was the personal attack at the end necessary?

Re: GWT 2.0: So good it's ridiculous

#8
GWT always sounds interesting, but I am underwhelmed by the application gallery. Every app looks like a draft version of gmail, google maps or google wave. Any links to impressive interfaces (non google-built)?

Re: GWT 2.0: So good it's ridiculous

#9
post #7

How could trading the expressiveness of JS for the expressiveness of Java without the commensurate increase in performance be "So good it's ridiculous".

Why ask this forum when the article explores this in detail?

Does it, really? Most of the optimizations mentioned in the article (compression/obfuscation, module system, yslow integration) or in these comments (debugging, refactoring, auto completion) are all available/possible in javascript alone. What tangible benefits require Java's type system?

Re: GWT 2.0: So good it's ridiculous

#10

Earlier quoted context omitted.

You clearly didn't RTFA. I'll give you my personal reasons for liking GWT in a few short bullets. 1. Better tooling - IDE refactoring when I need to change things. Red squigglies when I make a typo or reference something thats not there. A real debugger with breakpoints for finding bugs. Auto completion and auto style formatting so I dont have to type so goddamn much. 2. Compiler optimizations - Your code gets faster…

Was the personal attack at the end necessary?

Agreed.
Post reply on HN