Flatiron, A framework for Node.js
flatironjs.org
flatironjs.org
Now, it's been a few months, so take what I said with a grain of salt as it may have changed for the better. In fact, I'd love to use the framework.. that's why every month I'll try a pet project with it and see how stable it has become :)
Those negatives aside, I think it's a pretty solid framework.
Personally, I'm moving away from using frameworks. Just starting to bang together all of the awesome modules from npm. (Mostly inspired by Issac's npm-www[1] for npmjs.org)
if i'm not mistaken, that is the entire point of Flatiron. just a collection of independent modules. use as much or as little as you want.
from first paragraph...
"Philosophy No one agrees on frameworks. It's difficult to get consensus on how much or how little a framework should do. Flatiron's approach is to package simple to use yet full featured components and let developers subtract or add what they want."
> DSLs (Domain Specific Languages) such as <%=foo%> or {{foo}} reduce portability
I would argue, well documented template DSLs increase portability among developers, which is often more important than portability among frameworks.