-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments
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 |
(Y) |
@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 |
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? |
@ayushagarwal95 @aneesh-neelam @kunagpal |
Sails.js has a lot more middleware, makes it easier to maintain. |
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?
The text was updated successfully, but these errors were encountered: