3 ms·
I've looked the past week into sails.js. It brings a really cool new way to MVC Frameworks and makes it easy to do certain aspects. What I missed (and that's wh
by mweibel 14y ago
I've looked the past week into sails.js. It brings a really cool new way to MVC Frameworks and makes it easy to do certain aspects.
What I missed (and that's why I'm using express.js now) is the documentation (lacking) and testability (lacking as well).
Also the ORM is really lacking. I'd recommend the authors to look into an existing ORM (sequelize or node-orm2) instead of creating an own one.
Sails certainly needs more polishing but I look forward to use it in the future at some point, because I really like what it wants to accomplish.
If you like certain aspects (exposing models via REST, policies etc.) it's really easy to do in express.js as well.
- mikermcneil 14y agoHi mweibel, I originally used Sequelize, but we wanted (a) noSQL support and (b) a bundled in-memory database. Waterline has very good test coverage, and it's professionally maintained by my Node.js studio, Balderdash. We invest heavily in its development, because it makes our client projects better and faster. Happy to answer any other questions about why we built our own ORM.
- mweibel 14y agoOk I understand the decision now. Surely both (sequelize and node-orm2) aren't the one and only solution yet but I needed some stuff to be supported which you didn't (yet), e.g. indexes or something like that. Did you have a look at jugglingdb? I don't use it also because of similar reasons why I didn't want waterline but basicly I think it's more mature than waterline is.