> I'm not talking about a re-write here, I'm talking about new projects. For > new projects, I can't see a compelling reason for picking GWT, if the devs > are going to have to understand JS to use GWT then it is better to invest > up front time in getting them familiar enough with JS to use it for the > whole project. This is the decision we have taken in my organization. >
If you just want to write that new app thingy that can do 3 things very well and your client side code never reaches a critical size then fine, I guess I would also skip GWT. But if you have a 500-5000 KLOC client side application then its a totally different story and you quickly wish that you would have used GWT/Java or a different language with better tooling support than JS. So THE compelling reason for picking GWT is your expected app size. Even for small apps for which I might want to skip GWT I would, at least, use TypeScript to put as much type information as possible into my code to help devs and IDEs to reason about code. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/0b137ec1-3397-45ee-8f87-2d3002606302%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
