2068837226

If you’ve been following the JavaScript community during the past few years, you probably noticed a cornucopia of new libraries and frameworks.

There’s an NPM package for almost everything you can imagine. Growth is awesome, but if you’ve examined generations of bacteria evolving over the course of hours then you know the down side.

Atrophy

For every amazing library on NPM there are many more abandoned, half finished, or poorly documented projects. Thus is the nature of growth.

I built this website with a content management system using sails.js in 2014. I used sails.js because it resonated with my development philosophy, but it was still unclear where the framework is going — if it’s going to succeed or fizzle.

Growth

Recently I saw Sails.js pop up again. Not once, but twice!

The first time, I was discussing JavaScript frameworks with a friend online. He mentioned that he was actually learning about Sails.js.

My friend didn’t have any prior experience with Ruby on Rails, unlike many of the early Sails.js adopters. I never promoted it or discussed it with them either. My friend found the framework organically.

More recently, I noticed Sails.js on Hacker News via a link to a lesson on Platzi.

The public reaction was predictably critical, but in a positive way. When the critics commented, instead of listing reasons to avoid sails.js, they listed what sails needs to do to fill the gap to becoming a production tier framework.

Coming this far in the eye of the public is a great success for the sails.js framework.

Ultimately, that persistence distinguishes a “fly by night” JavaScript framework from a production.

Sails.js isn’t there yet, but it’s well on the way.