And how do you debug a problem now? First you'll have to find the problem in the automatically produced Javascript, then find out how that relates to your Java files that were used to produce the Javascript. What if the tool has a bug? It'll take you a very long time realizing that.
Well, according the the GWT website, that's not true.
One of the big advantages of GWT, or so is it advertised, is that you can develop *and* debug your app directly in Java, not having to mess with the Javascript at all.
From the GWT overview:
Google Web Toolkit (GWT) is an open source Java development framework that lets you escape the matrix of technologies that make writing AJAX applications so difficult and error prone. With GWT, you can develop and debug AJAX applications in the Java language using the Java development tools of your choice. When you deploy your application to production, the GWT compiler to translates your Java application to browser-compliant JavaScript and HTML.
Here's the GWT development cycle:
1. Use your favorite Java IDE to write and debug an application in the Java language, using as many (or as few) GWT libraries as you find useful.
2. Use GWT's Java-to-JavaScript compiler to distill your application into a set of JavaScript and HTML files that you can serve with any web server.
3. Confirm that your application works in each browser that you want to support, which usually takes no additional work.
According to Hollywood most programmers haven't discovered how to use a mouse. Sure, we type fast, but a mouse is a very useful tool and there's no reason we'd abandon it. While we're dispelling stereotypes, I'd also like to say that not all programmers are hot-pocket eating virgins who play WoW. Some of us exercise and have active social lives. Some have even had SEX! Holy Crap!
That guy obviously doesn't use emacs.
"Mobile Phone" or just "Mobile"In the article summary, one of the reasons why the word "Cell Phone" should become obsolete is that it seems that voice calls or the least used function of most phones. So the main point is that it's not really a phone anymore.
This isn't quite what I'd call "native".
I don't have much faith in humans surviving that long, population growth problems, limited resources, the possibility of 'real' atomic war...
Not to mention that in 5 billion years, Earth will be totally vitrified by a red giant (namely, the Sun).
Ever heard of XML+XSL ? And all the other stuff that make XML frickin' awesome ? http://en.wikipedia.org/wiki/Extensible_Stylesheet_Language
I can.
But I must admit I'm a real Dickhead.
"And then I'm gonna come back there and put my foot in your ass if you say "and then" again!"
Hastur Hastur Hastur ?
Maybe they're dense about grammar.
"Get together... One more time..."
Well, according the the GWT website, that's not true. One of the big advantages of GWT, or so is it advertised, is that you can develop *and* debug your app directly in Java, not having to mess with the Javascript at all.
From the GWT overview
Here's the GWT development cycle:
1. Use your favorite Java IDE to write and debug an application in the Java language, using as many (or as few) GWT libraries as you find useful.
2. Use GWT's Java-to-JavaScript compiler to distill your application into a set of JavaScript and HTML files that you can serve with any web server.
3. Confirm that your application works in each browser that you want to support, which usually takes no additional work.
I'm not quite sure that more than half the slashdot population can find themselves in vaginas...
That guy obviously doesn't use emacs.
"Mobile Phone" or just "Mobile"In the article summary, one of the reasons why the word "Cell Phone" should become obsolete is that it seems that voice calls or the least used function of most phones. So the main point is that it's not really a phone anymore.
... and, of course, with a license that allows the user to redistribute freely the modified version so anyone can benefit from the improvements made.