2 ms·

Sounds like at least a few of those are legit concerns, if not bugs. Like I said, I don't really know much about Sails. I was just interested in the idea that

• traviswebb 11y ago
  If you only knew how much work needs to be done on Sails.js, you'd understand how inadequate 10 commits per month is :)
• hitekker 11y ago
  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 https://github.com/django/django/pulse/monthly. For rails, 468: https://github.com/rails/rails/pulse/monthly 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_dead_dying/cmu0sj9 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.