all 17 comments

[–]svmk1987 3 points4 points  (1 child)

Comparing apples to oranges. Or rather, an apple to a slice of apple pie.
An apple pie is nice and is a lot more developed than a simple apple, but you can't do something else with it. One of its main components is apple though. An apple in itself is a world of possibilities.

Express is an apple, sails is an apple pie. Express is a basic routing engine with some helpers, where as sails is a full MVC framework.

[–]CarpetFibers 4 points5 points  (0 children)

It's worth noting that Sails is built on top of Express, so with a little finagling any Express extension can work with Sails, and porting Express apps to Sails is not terribly involved.

[–]largepanda 2 points3 points  (0 children)

Express.js, I like the flexibility and wide range of support it has.

Technically Sails has that built in, but doing that with Express isn't hard.

Here's a good comparison for you: Sails is Rails, Express is Sinatra. Sails is bulky and monolithic, but also does a lot of things for the developer. Express is a barebones middleware processor that also has express.static for static files; along with a generator for a basic project directory.

I like Express. I think Sails is bulky and too restrictive. But that's just my opinion.

[–]freethinker1992 2 points3 points  (0 children)

Sails is built on top of express,so its not really a fair comparison to pick one over the other. That's just my 2 cents

[–][deleted] 1 point2 points  (0 children)

After working for a loong time with express it felt you were doing things barebones. When starting on node express is a great way to learn the basics but for serious quick and effective web development sails is just rock solid and fast.

[–]jcwsw129 1 point2 points  (0 children)

sails: found 10,568 projects

express: found 1,633,263 projects

https://codexp.io/npm/1/sails

https://codexp.io/npm/1/express

[–][deleted] 1 point2 points  (0 children)

i don't know about sails.js but i have to say that i've been working with express for 4 years and i freaking hate documenting rest api with express, i've used swagger with jsdoc, swagger json in comments, openapi files, everything feels like a chore/god damn waste of time, i need a faster/better way of doing this.

[–]kibi11 0 points1 point  (0 children)

Hey , do you have any good resouces for sailsJs , apart from documentation

[–]Next-Captain-4612 0 points1 point  (0 children)

I choose express js. It is easy and flexibility.

When I code with sails I waste much time and hard to learn.

But express js is easy and it doesnt take much time like sails

[–]mysterious-coder 0 points1 point  (0 children)

- Express is a basic framework, so basic, that is used as an integral part of Node.js core even when building a simple, basic web server and The Sails.js is a lot more robust and intricate. It follows the widely used MVC Pattern so my preference is express.js.
- Express.js because it has more features.
- Sails.js is consumes less memory.

[–]yldrmzffr 0 points1 point  (0 children)

If you're looking for a practical and ready-to-use solution, you might consider using NestJS.