There is no 'spreading thin'. All these languages, design patterns, idioms, hacks all start to look the same, regardless of language, after you get enough experience and then it is just picking the right tool for the job.
On Oct 22, 11:05 pm, mattkime <mattk...@gmail.com> wrote: > I think its correct that I'd become a java developer, even if I'd > slide in slowly. I enjoy learning new tech but I don't want to spread > myself too thin. > > I've been examining various front end technologies lately and cringe > whenever someone claims a particular framework "fixes" something in > javascript. Its almost never a javascript problem but a dom problem or > its just a variation from how java works. Additionally, there is no > inherent barrier to writing large apps in js any more than there is in > java. > > The determining factor as to whether we'll use GWT will be how we want > to build our dev team. As it is, our java developers are quite busy so > i couldn't understand why we'd saddle them with more responsibility. > That said, its a decision for the people above me. > > I'm not sure if its an inherent part of the approach but I fault GWT > for largely ignoring page based content loading and navigation. It > would be preferable if the content was loaded into an html page before > any js was attached. GWT v3? > > And one more outstanding question - how GWT would relate to our > existing codebase which is a mix of spring/jsp and xslt - yes, its a > mess. Other front end technologies seems like they'd merge a bit > easier. > > thanks for the advice! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
