I'm really interested in how it compares to what express does. How is it the same, how different? However since I'm reading this from the office between doing actual work I've not got time to read this version.
I may or may not remember to come back and check it out after work.
Anyways, all of that is intended as a round of constructive criticism. At the end of the day, it is what it is.
http://blog.nodejitsu.com/scaling-isomorphic-javascript-code
The proposed Resource-View-Presenter model is a bit of a brain bender.
Anyway, that aside, I agree -- this is described as a framework "initiative", and that page has no links to actual code, making it sound like a mere proposal.
However, looking back at Nodejitsu's blog, it looks like they have a post with a more cogent explanation... and github links:
`plates` is essentially a loose html-parser. The only reason it exists is because `weld` is too slow right now for mass consumption. `plates` is intended to ensure that developers have a way to template without DSLs since a lot of people want to keep their markup clean.
I totally endorse the anti-template philosophy. But I want a bit more, like targeting attributes (eg, the href of an anchor, the value of an <option>) and replicating a class-selected fragment for welding data from arrays.