Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sails.js #8

Open
aneesh-neelam opened this issue Dec 6, 2014 · 6 comments
Open

Sails.js #8

aneesh-neelam opened this issue Dec 6, 2014 · 6 comments

Comments

@aneesh-neelam
Copy link
Member

Sails.js is quite different. It may be based on express, connect etc. but is not the same. Check out Sails.js documentation.

Why has you merged an express application and sails application in the sails branch?

@tjwebb
Copy link

tjwebb commented Mar 30, 2015

Hey sails.js isn't a bug! Let us know if we can help. It is just express underneath, the rest is a suite of configurable hooks that loads additional middleware.

-- the sails.js team

@kunagpal
Copy link
Member

(Y)

@kashishbest
Copy link
Contributor

@tjwebb He was not referring to sails.js being a bug, he was referring to the merge as a bug. Hope this clears the confusion. And I would love to get in touch with you, and get to know sails better

@kashishbest
Copy link
Contributor

Do we really need to move to Sails, I mean, yes, Sails does provide another wrapper around Express, as per my initial research. But unless we are really looking a huge improvement in our current system, why should we do, unless we are looking at a learning curve for the developers?

@kashishbest
Copy link
Contributor

@ayushagarwal95 @aneesh-neelam @kunagpal
Your opinions?

@aneesh-neelam
Copy link
Member Author

Sails.js has a lot more middleware, makes it easier to maintain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants