Re:Status of Sails.js
by traviswebb on Thursday December 31, 2015 @10:34PM
(#10821022)
If you only knew how much work needs to be done on Sails.js, you'd understand how inadequate 10 commits per month is :)
Depends on the kind of projects. In the "heavy" web framework category ("we take care of lots of the busy work for you"), an established project like Django can expect 256 commits a month:
https://github.com/django/django/pulse/monthly.
For rails, 468:
https://github.com/rails/rails/pulse/monthly
ExpressJS, on the other hand, only had 5 commits this past month, but one could argue that it's not as "heavy" as SailsJS and others are trying to be.
I agree commit count by itself is not a good pulse on a project's life, but, as this thread shows, there's a lot of issues left unresolved. Not mentioned yet one of the lead developers posted on Sails.js future right here:
https://www.reddit.com/r/node/comments/2p2i40/is_sailsjs_dea...
The most important line is:
> There's not much really left to add to Sails other than bug fixes at this point.
All these indicators together = a dead project.
Like I said, I don't really know much about Sails. I was just interested in the idea that ~10 commits per month would be insinuated to be an abandoned project.