On 10/28/2010 07:02 PM, Mark Volkmann wrote:
I agree! I prefer implementing services that return JSON and creating HTML views of that data using jQuery in the browser. I recommend running JSLint on all your JavaScript code. It has saved me a lot of debugging time.
Architectural speaking, only exposing REST from the server and connecting a rich client is clearly a solution that I like more than others (I recall that I consider a 'webapp' different than a '(dynamic)' website; the latter makes sense and it makes sense that presentation is generated on the server, if not other because of searchability). But I don't like JavaScript (*) at all and I wouldn't like to use it in any way. So I suppose those framework that generate JS out of Java (or other languages that one likes best) will have some success - clearly, evolving from what they do now.
Clearly the pure approach that Clay describes has the advantage of being portable everywhere, including iPhone, Android, WebOS and others.
(*) In other words, I *could* appreciate JavaScript as a VM - à la GWT - , rather than a language.
-- f.g. -- 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.
