On Mon, Nov 30, 2009 at 8:32 AM, Simon Brocklehurst <[email protected]> wrote: > > On Nov 30, 1:43 pm, Mark Volkmann <[email protected]> wrote: > >> I used to think that until recently. > > Sorry, I don't think I was clear in my meaning. I think JavaScript- > based approaches to developing web apps running in the browser (like > JQuery or GWT) are, in the end, the best available choices for > building web apps (compared to Flash/Flex, Silverlight, Java/JavaFX). > > When I said it was a poor choice, what I meant was that the > development process is old-fashioned, clunky and error-prone (IMO). > That means it's hard to get really high-quality results when building > a complex application (from a development point of view) compared to > using some other technologies e.g. those based on the .NET or Java > platforms. > > I believe there's plenty of room left for innovation when it comes to > technology platforms for creating browser-based apps. IMO, no-one has > a good solution yet.
Ah ... I can see that. One thing I recommend is making jslint part of an automated deployment process. I set up mine so that every time I deploy my web app it looks for JavaScript source files that have been modified since the last deploy. It runs jslint on those and the deploy fails if any issues are reported. That has saved me a lot of debugging time. Still, as you say, there is room for improvement. -- R. Mark Volkmann Object Computing, Inc. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. 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/javaposse?hl=en.
