Hamster, yes, this was the kind of thing I was worried about seeing in a year:
"yeah of course it's the GWT again" Ha. Thanks for sharing. Good stuff. On Friday, October 5, 2012 1:12:52 PM UTC-4, HamsterofDeath wrote: > > YES! > > if i had to mess (and i mean mess) around with jsp files, webflows, > generated javascript in tags, embedded javascript in jsp files... i > wouldn't keep that job. javascript is nice for almost logic-less things > like the whole jquery stuff, but as soon as you have to run logic in the > browser, javascript (or rather its lack of mandatory documentation aka > static typing - or worse: it expects a special context that is > dynamically generated on in random files that are mentioned nowhere) > will come back and bite you. > of course the GWT isn't the only way to avoid melee fights with > javascript, but it's one of the good ways that works for us in > production since more than 2 years. we never had a bug where some > developer would say: "yeah of course it's the GWT again". > > Am 05.10.2012 17:53, schrieb Charlie Youakim: > > 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/-/7HVAiaphHqwJ. > > To post to this group, send email to > > [email protected]<javascript:>. > > > To unsubscribe from this group, send email to > > [email protected] <javascript:>. > > For more options, visit this group at > > http://groups.google.com/group/google-web-toolkit?hl=en. > > > -- > > -- 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/-/XoBOW65qJYQJ. 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.
