Why GWT?

From these points of view, transition doesn’t seem to be a good idea, even though you might find out that GWT resources are pretty expensive. The trick why those folks are so expensive is that they specialize a lot on GWT backend stacks, which is an enterprise class java technologies. Instead, if your back-end stack is non-java, you could happily hire senior javascript guys & easily convert them into GWT devs. Our 2+ years experience showed that it works pretty well — monthly learning curve and your dev-team is able to use all of GWT strengths.

How to leverage existing Javascript solutions?

Javascript is so widespread today and there are tons of cool stuff already built. How is it possible to grab some piece from that tasteful cake?

You’re probably looking at these:

• Cost of javascript resources is pretty attractive
• Re-use of existing open-source javascript code

But wait, is GWT really java? Nope. At the end it’s the same old javascript which is used everywhere. What this means for you as business, is that you could still leverage any javascript solutions out there.

In the case of existing GWT application, the solution seems to be pretty obvious. Core GUI front-end may be maintained using GWT & third-party extensions can be easily built using plain javascript. However, this does bring a few of technical problems:

• There is a need to invent a well designed interface for integration of GWT Core app and third-party javascript
• There is a problem of css-styling of core app by means of third-party extensions

Those are a real technical problems, which you just need to spent some time to resolve. This way, you’ll continue to happily use GWT for the “core” stuff & leverage javascript extensions which might add a huge value to your application.

Page 4 of 4 | Previous page