News for hackers. Stuff that matters.
Re:What is wrong with GWT. by rbanffy on Tuesday October 11, 2011 @10:16AM (#3098624)
Independently of the merits of GWT or the follow-up apology post, Java is an awful language to write web applications with. Languages like Ruby and Python (mostly when associated with frameworks like Rails or Django) allow you to become much more productive, yield a much smaller codebase and much lower long-term maintenance costs.

As for the JavaScript side, if you find it daunting, you may try Coffeescript or even Closure (which provides some Java-developer-friendly limits to JavaScript).

Java has its strengths, but writing web applications isn't among them.

Re:What is wrong with GWT. by tcarnell on Tuesday October 11, 2011 @11:03AM (#3098825)
Absolutely. I am at a loss as to why people use Java for Internet facing sites and apps. Of all the things Java 'should' be used for (embedded apps and desktop applications) it gets most used for the one thing it wasn't designed for - the web.

So...was GWT developed for Java web developers that didn't want to learn Javascript? Javascript is just one of the things you have to know how to use to build a modern web site or web application.

Re:What is wrong with GWT. by PaulHoule on Tuesday October 11, 2011 @10:44AM (#3098738)
I've got complex feelings about Java.

The comparison with Ruby and Python isn't really fair. A better comparison is C#, which is like Java in spirit but has a large number of incremental improvements over Java.

Underlying it all, Java has an attitude that concision doesn't matter. One reason why people don't do anything interesting with generics because you always have to write

GenericContainer<AnotherGenericContainer<ArbitaryTypeA>,AbitraryTypeB> = new GenericContainer<AnotherGenericContainer<ArbitaryTypeA>,AbitraryTypeB>();

C# has var, extension methods, function pointers, generics without type erasure and many other little things that show respect for the programmer. You realize then that the "problem with Java" isn't an all or nothing thing (static types suck), but an obstinate cultural attitude that's gone on for 15 years.

C# might not be as concise as some languages, but it shows you can have something a lot like Java that isn't as bad... and that makes it clear how outrageous Java is!

Re:What is wrong with GWT. by rbanffy on Tuesday October 11, 2011 @11:05AM (#3098835)
> The comparison with Ruby and Python isn't really fair.

It's fair because there is nothing stopping you from picking up any of them, a decent framework and be orders of magnitude more productive than either a Java or a C# developer. C# is a better language than Java, but it still comes short when it comes to developing web applications.

There are hugely successful apps written in C# and Java, I agree, but their existence is owed more to the brilliance of their developers than a brilliant choice of tools.

Re:What is wrong with GWT. by PaulHoule on Tuesday October 11, 2011 @11:24AM (#3098934)
"Orders of magnitude more productive" isn't true -- except in the case that the productivity of people on a failed project is zero.

For projects that get completed, I could believe two or three... Maybe more in cases that are trivial to do with rails.

The nightmare I've seen happen with Ruby projects is that the "developers" are often web designers who know how to do things that are easy (or trivial) to do with rails, but get in over their heads rapidly.

Python, on the other hand, has a culture of doing the 20% of the work that gets you 80% of the way to production, announcing that they're done, moving on to a greenfield project, and then laughing at the "Blub" programmers in PHP and Java who work so much harder to get things production-ready.

Java's greatest strength, on the other hand, is it's greatest weakness. Java has a huge number of libraries that make it possible to do wonderful things, like Lucene and Hadoop. There's "more than one way to do it", which means that real-life systems might have 5 different JSON libraries used in different parts of the system. A programmer who needs to work on a small part of an application might need to wait for Maven to download 650 megabytes worth of JAR files. When you have 650 megabytes of dependencies to deal with to work on 65 kilobytes of code, it takes a very small amount of bullshit per kilobyte in the dependencies for you to spend more hours messing around with the build system than you spend developing.

Re:What is wrong with GWT. by rbanffy on Tuesday October 11, 2011 @01:01PM (#3099350)
I have to disagree with your two misconceptions:

> Ruby (...) "developers" are often web designers who know how to do things that are easy (or trivial) to do with rails

> Python (...) has a culture of doing the 20% of the work that gets you 80% of the way to production, announcing that they're done, moving on to a greenfield project

I have met, during my career, a lot of incompetent professionals like the ones you describe above. Most of the time, they work with "safe" technologies, the ones they are sure there will be demand for. Java, PHP, C#, ABAP and VB are their favorite tools. When you see someone proposing something crazy, like using Python (or Ruby, or Smalltalk, or Lisp, or Erlang) on a very enterprisey application, they are either lunatics or just very, very smart. BTW, to be fair, I've seen lots of very competent Java, PHP, C# and even VB programmers. But they are exceptions, not the norm.

And no. I have developed tons of Python code from concept to production. If we have this 80/20 culture, I have, so far, managed to be completely oblivious to it. The main difference between your anecdote and Java projects I have seen in the past is that nobody but management claims they are done.