Flatiron, A framework for Node.js(flatironjs.org)
flatironjs.org
Flatiron, A framework for Node.js
http://flatironjs.org/
7 comments
I would concur with you on your caveat. There is activity in all of the repositories, but it also feels sometimes like the projects are drifting sideways. I'll also add that the documentation could be a lot better. I'm primarily familiar with the Resourceful component, and I frequently have to go back to an early version of the README (as well as perusing the source code constantly) to recall how things are supposed to function.
Those negatives aside, I think it's a pretty solid framework.
Those negatives aside, I think it's a pretty solid framework.
so is this the minimalist's framework? isn't the whole point for a framework to make your life easier? (i.e. express/derby)
Anyone know of any comparisons?
expressjs is the most frequently used framework. Geddy is another one. Socketstream is also being developed.
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)
[1] https://github.com/isaacs/npm-www
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)
[1] https://github.com/isaacs/npm-www
>>> Personally, I'm moving away from using frameworks.
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."
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."
This is a pretty good one: http://ocdevel.com/blog/nodejs-frameworks-comparison
How does this compare to Meteor? (http://meteor.com)
I really like what they've built here, but...
> 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.
> 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.
I have started using plates and director for client side projects. Loving it.
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 :)