Web apps are going back to the client/server model where the client is
the browser, the UI actually runs on the client, and the client is built
with client-side technologies (CoffeeScript, Dust.js, Backbone.js,
LESS/Sass, Twitter Bootstrap, etc).
I don't think that server-side component frameworks play well with this
model, but there is a layer of tooling that these frameworks can
provide. For instance, Play 2 has the usual server-side templating, but
also has great support for compiling CoffeeScript, JavaScript, Less,
etc. Server-side frameworks can assist with the development of the
client-side code.
My favorite parts of the new model include being able to edge cache the
entire client-side of a web app and moving session state out of the
server and onto the client (where it belongs). Those two things can
lead to much better scalability.
-James
On 12/26/2011 06:07 PM, vineetb wrote:
HTML5 by itself won't be sufficient. Let me clarify.
For example, with Flex/GWT most of the user interface code is written
in Flex/GWT and not using web frameworks.
You would need javascript MVC framework and javascript templating
engine. Backend services could be written to output json or xml.
Linkedin has started following this approach. See Leaving JSPs in the
dust: moving LinkedIn to dust.js client-side templates (https://
engineering.linkedin.com/frontend/leaving-jsps-dust-moving-linkedin-
dustjs-client-side-templates)
- vineet
--
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.
