After using GWT for a year as the basic tool for a project, I am not sure if I would choose it again. I would, but only for a certain type of web apps.
I can't say it is bad. Actually, it has been pretty good. But, somehow when I look at all the other development environments out there, some of them look better. ekidd put it pretty well, actually.
The best side effect of using GWT has been a lot of business logic on the client side.
The worst side effect of using GWT has been a lot of business logic on the client side.
Comments
After using GWT for a year as the basic tool for a project, I am not sure if I would choose it again. I would, but only for a certain type of web apps.
I can't say it is bad. Actually, it has been pretty good. But, somehow when I look at all the other development environments out there, some of them look better. ekidd put it pretty well, actually.
The best side effect of using GWT has been a lot of business logic on the client side.
The worst side effect of using GWT has been a lot of business logic on the client side.
How is your choice of where to place your business logic GWT's fault? Isn't that a choice you would have to make judiciously with any tool?
You are correct, ofcourse. It is not the fault of the tool, but of a developer. The tool just made it easier.