[AlexC04]

I'd like a simpler explanation of how it all works. With colorful flow charts and graphs.

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.

[akavlie]

If you want colorful flow charts, there are plenty at the "Isomorphic" link:

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:

http://blog.nodejitsu.com/introducing-flatiron

[AlexC04]

Thanks so much for this! The graphs are exactly the kind of "conceptual flow" I like to have to give me a 1000 meter view of what's going on.

[mcantelon]

Express is quite low level, with many frameworks built on top of it. This appears to be higher level.

[justatdotin]

yeah, but, it's not immediately clear to me why they built sugarskull instead of a client library to match connect's routing (I've used sammyjs for that purpose) and while I do appreciate the philosophy of plates (I've done something similar), I wonder why wasn't that implemented as an express 'template engine'. I'm sure there's good reasons: I'd like them spelled out ;{)} looking good.