I can't see the difference that after 2 years and 40 developers get their hands on GWT.
Google doesn't have its confidence. The only product implemented by GWT in Google Google Wave is dead now. Remind me any other successful cases on GWT?
I have doubt how long GWT can last. Will Google abandon it?
This doesn't come down to GWT anymore, it now becomes larger concern of what language do you want to develop in. Weakly typed or strongly typed? Class based or object based (if you even go object oriented at all), etc, etc and all these old debates we've had a million times before.
Some really good points in there though. Currently the pro's certainly out-weigh the con's (IMO) If Google ever abandon it, we'll have no choice to write CoffeeScript or jump on whatever new tech. (Dart) that Google will abandon a few years after release ;)
I would ask for a language that helps me enforce good design practice. Java is verbose and at times a pain in my backside. But having to write a UI in a Javascript framework I want the type safety and separation of ideas that Java enforces. That's why I would take GWT for AJAX apps over anything else.
Dean Budd - 2011-11-24 15:16:59+1100 - Updated: 2011-11-24 15:17:42+1100
Currently we are feeling a bit of pain having to support two versions of GWT in the same web application, 1.7 (way to hard to upgrade) and 2.3 Even with this hassle, the benefits are still far too great not use the tech...
I don't mind PHP as at least it can enforce good design, especially in a framework like Symfony. I think everyone knows where I nail my colours in regards to Ruby.
Can't understand why less and small is not beautiful if you can just get the job done. Don't you get headache every time when someone says it's big and heavy? Sorry I haven't convinced GWT is good enough let me put my money on, even it's Google backed.
Playing jQuery wrapper for an application, playing Ajax built in jQuery now.
As concise as a poem, as sharp as a scalpel, jQuery gives you a blissful experience than what you can ask I reckon.
Dean Budd - 2011-11-24 15:36:01+1100 - Updated: 2011-11-24 15:37:28+1100
+Terrence MiaoJQuery is perfect for one-man shops or even small teams of about 5... watch the quality of the code degrade rapidly after that, if you don't have extremely disciplined JavaScript developers
+Terrence Miao But isn't that the point. Developers can try to be as well disciplined as they possible can be, but modern day applications require so many ideas (DB, business tier, web tier) and technologies that we get overwhelmed by the complexity. So you should want a language (and frameworks) that force as much of that complexity into the tools (eg the compiler).
I will call that experienced, efficiently, but not dogmatically follow good practice and design pattern than extremely disciplined.
Good tools, framework and computer language give you a solid foundation to build a "house", but doesn't guarantee you a finish, doesn't guarantee your "house" can still stand there 100 years later.
How do you design, how do you make selection, how do you engineer, how do you manage the project, that's developers' creativity parts. Spanking developers bare butts, under the form of discipline, won't let them smart up.
In the end, software is a human being's product. If there are tools and compilers are so good, anyone can just press a button to get work done. Why do we need to have a hot debate here for?
The tools also define whether your "house" is there in 100 years. If all you have is a hammer, then screw everything else. Tell me that's going to last.
As +Dean Budd has rightly pointed out, it can all dissolve into a mess.
+Alex Megremis Agreed. However, it's also not so much about how long the thing lives, but how adaptable is in in the meantime. You will see countless codebases become unmaintainable before their time is due. Certain languages help this happen quicker than others.
Google doesn't have its confidence. The only product implemented by GWT in Google Google Wave is dead now. Remind me any other successful cases on GWT?
I have doubt how long GWT can last. Will Google abandon it?
Plus, ANY codebase will look like a used up Thai transgender stripper, after 2 years and 40 developers have had their way with it.
If Google ever abandon it, we'll have no choice to write CoffeeScript or jump on whatever new tech. (Dart) that Google will abandon a few years after release ;)
No, I love it!
It fosters rethinking. Don't get trapped into a 10yo mistake - take the hit and do it from scratch - better.
Even with this hassle, the benefits are still far too great not use the tech...
:)
Playing jQuery wrapper for an application, playing Ajax built in jQuery now.
As concise as a poem, as sharp as a scalpel, jQuery gives you a blissful experience than what you can ask I reckon.
http://www.quora.com/What-programming-languages-is-Gmail-implemented-in/answer/Paul-Buchheit
Fair enough - I stand corrected.
Good tools, framework and computer language give you a solid foundation to build a "house", but doesn't guarantee you a finish, doesn't guarantee your "house" can still stand there 100 years later.
How do you design, how do you make selection, how do you engineer, how do you manage the project, that's developers' creativity parts. Spanking developers bare butts, under the form of discipline, won't let them smart up.
In the end, software is a human being's product. If there are tools and compilers are so good, anyone can just press a button to get work done. Why do we need to have a hot debate here for?
As +Dean Budd has rightly pointed out, it can all dissolve into a mess.
That's the only reason we'd ever be allowed remotely modern languages, libraries etc