Definitely YES! We are using vanilla GWT, and it is great, just documentation is not that helpful. If you want to create some more advance things, you will need to dive into GWT source.
On Friday, October 5, 2012 5:53:17 PM UTC+2, Charlie Youakim wrote: > > I'm deciding on whether to switch my team to GWT. I think the biggest > thing for me as the tech lead for the company is "Are you happy with your > choice to use GWT?" > > My reasons for thinking to switch: > > -Javascript is a fast and free language, sometimes too fast and free for a > large team. Coding standards can vary from developer to developer, and > maintaining architectures can be difficult > -Javascript mistakes are only caught in runtime. The fact that GWT(Java) > would catch 90+% of our simple mistakes makes me more confident that our > clients won't. > -Javascript allows for rapid development, but not so rapid bug fixing. > -Strict Java coding + a strong architecture at the outset creates a great > foundation to build from. I've even seen this in my firm's Android apps. > They are very stable. > > But for me, I'd really like to hear from developers active in the > community. Are you happy? Or do you wish you went a different route? My > goal is to have my dev team work more on new projects rather than fixing > old projects. I am hoping that GWT can help with that. thoughts? > > -Charlie > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/ij8qInubkx8J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
