Often times Google Web Toolkit (GWT), Google Gears, Google App Engine and Google Apps are seen as one product. And yes, they are related, but they are also very different things.
Google Web Toolkit is a framework designed to work around "all" the tedious work when writing browser applications. To accomplish this a radical approch is chosen, namely that you write your application in Java. Not the kind you execute in an applet (remember? aaaaargh), instead the code is compiled into crossbrowser compatible javascript!
Using Eclipse makes this work very well, and because of the Java HotSpot compiler, you have an environment where you can retain the rapid development cycle of write->reload, that you are used to from traditional http://notepad-plus.sourceforge.net/ development. But even better, you can debug the code in Java - an experience that is in another league compared to javascript debugging.
Google Apps is actually an end user offering from Google that resembles how many intranets are constructed. You know, a central place for documents, calendars, communication etc.
However, Google App Engine is something completely different. Or not. Actually this is a cloud based hosting environment that can host your GWT solutions if you should choose so. Google App Engine also what lies beneath Google Apps. It supports Pyhon instead of Java, if that floats your boat better.
Google Gears is another go at a browser plugin. Unlike most other plugins however, this one extends the browsers capabilities instead of creating it's own "universe". In short, Google Gears makes it possible (in a sandboxed way) to make browser based (possibly offline) "desktop" applications, controlling a local storage area, adding nice icons etc. Much of this is (will be) covered in html5, when that time is reached.
So, all of these technologies enable web based application development, but they are spanning different parts of the process, mainly split into the client and the server side of things.
Ingen kommentarer:
Send en kommentar