Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Status of Sails.js

github.com

Post reply on HN
Print view View original

11–20 of 74 posts

Re: Status of Sails.js

#11

Post by dbg31415 »

Mike wrote in here, sounds like they are just busy working on Treeline. My read: doesn't help having an ex-employee / collaborator telling everyone Sails isn't supported any more. That just seems like trolling.

https://github.com/balderdashy/sails/issues/3429

> Hey Cody, thanks for sharing your concern. Apologies for the lack of transparency from our end- it's coming from a place of limited resources, not deliberate opacity. Like you said, we're a small team spread across a few large projects right now; and it's part of why we've been in more of maintenance/stability mode with Sails and Waterline over the past 9 months.

> Another thing has happened too: we've become more attuned to the full lifecycle of development with a Sails app. The work we do outside of open-source has always been a huge influence on Sails-- I mean, I firmly believe the reason why the framework has helped so many other folks is that we've always focused on solving real-world problems that we have ourselves. Now that we are a product company (as opposed to being focused on services), our team has become more attuned with the experience of working w/ a Sails app over the course of months or years (as opposed to the experience of the first 2-3 months). As you might expect, maintaining our own large-scale production deployment has drawn our attention to issues like security and performance more than ever before.

Re: Status of Sails.js

#12

Post by paulddraper »

fideloper wrote: post #2

I can understand doing this from a maintainer point of view - I'll bet this gets written in a better way using the lessons learned from the first version. Moving fast and breaking things seems par for the course in javascript land, I don't really try to keep up. I've ended up only using NodeJS for plumbing type apps (e.g. web hook listeners calling other APIs), definitely not for full on web apps, which I've found to…

You're going to love npm3 then. It installs different versions depending on the order you install them.

https://docs.npmjs.com/how-npm-works/npm3

Re: Status of Sails.js

#13

Post by paulddraper »

duhruh wrote: post #8
jph wrote: post #4

Compare the new Trails JS: https://github.com/trailsjs/trails The Trails project is developing thanks to Travis Webb and team, and his reasons are described in the pull request. The Trails README includes this intro: "Trails is built and maintained by former members of the Sails.js core team, and offers an upgrade path from existing Sails applications, but it utilizes exactly zero lines of code from the original Sail…

Yea I've noticed this too, mostly because Travis threw up a comment on multiple GH issues on my Sails library e.g. https://github.com/waterlock/waterlock/issues/99#issuecommen... I've looked over these issues and noticed Travis is just copy/pasting the same message stating "Sails.js is no longer actively maintained". It seems like this guy has a real vendetta against Mike (the creator of Sails) and is dead set on get…

Eh, to me it seems like someone who is really invested in a project and would like to see as much of the current Sails user base as possible contribute to the Trails community. May be more tact could be used, but I think he's doing a good thing.

Re: Status of Sails.js

#15

Post by chm »

jph wrote: post #4

Compare the new Trails JS: https://github.com/trailsjs/trails The Trails project is developing thanks to Travis Webb and team, and his reasons are described in the pull request. The Trails README includes this intro: "Trails is built and maintained by former members of the Sails.js core team, and offers an upgrade path from existing Sails applications, but it utilizes exactly zero lines of code from the original Sail…

By the way, http://www.trailsjs.io is a parked domain.

Re: Status of Sails.js

#16

Post by lopatin »

jondubois wrote: post #7
SignMeTheHELLUp wrote: post #3

I found SailsJs unfit for any projects that had even a moderately sized set of business rules. Partly due to Node's lack of threading and partly because SailsJs feature set was a weak or incomplete copy of 'real' frameworks which failed to meet needs once they had to offer anything more than an extremely light CRUD wrapper. I agree with fideloper that it's better not to use NodeJs or any of that mess of an ecosystem…

Node.js is fine. I'm currently contracting for a major company which is using Node.js in production and it's been great. I've worked on Python backends at my previous startup and I can say that Node.js faster to develop with. Linkedin also uses Node.js and they found a 50% increase in development speeds as a result after making the switch a few years ago.

It's less of a language issue and more of a framework/ecosystem issue, which is what I think the original commenter meant. The Node.js community is much more fragmented than Python. At least when it comes to web frameworks. Everyone has their own Node framework. Old ones often end up getting deprecated and neglected. So I think that's what people are referring to when they say that Node.js is an unproductive ecosystem. You end up spending way more time on the Github issues page of your framework than you would for the frameworks of other languages (Python, Go, ...) where, for the most part, the tools just work.

Re: Status of Sails.js

#17

Post by maxpupmax »

zensavona wrote: post #9
jondubois wrote: post #7

Earlier quoted context omitted.

Node.js is fine. I'm currently contracting for a major company which is using Node.js in production and it's been great. I've worked on Python backends at my previous startup and I can say that Node.js faster to develop with. Linkedin also uses Node.js and they found a 50% increase in development speeds as a result after making the switch a few years ago.

50% increase in development speed after making the switch from what ? I am certainly more productive in Ruby or more recently Elixir than JavaScript on either the client or server.

RoR, apparently.

http://highscalability.com/blog/2012/10/4/linkedin-moved-fro...

Re: Status of Sails.js

#18

Post by traviswebb »

chm wrote: post #15
jph wrote: post #4

Compare the new Trails JS: https://github.com/trailsjs/trails The Trails project is developing thanks to Travis Webb and team, and his reasons are described in the pull request. The Trails README includes this intro: "Trails is built and maintained by former members of the Sails.js core team, and offers an upgrade path from existing Sails applications, but it utilizes exactly zero lines of code from the original Sail…

By the way, http://www.trailsjs.io is a parked domain.

It's a parked domain that I own :) We're just recently pulling the branding and docs for trails together. We'll have a website hosted there soon.

Re: Status of Sails.js

#19

Post by kevinburke »

jakejake wrote: post #6

I don't use sails but I found the criticism of the project interesting because it has somewhere around 80 commits in 9 months. I guess we are in a time where our tools are expected to significantly change frequently? It seems like I have a disconnect with this mentality as we're running products where stability (reliability as well as API stability) and solid documentation are more important than constant innovation.…

> I don't know, perhaps sails is riddled with unfixed bugs?

I wrote about a fair amount of unexpected behavior with Sails/Waterline. Some of these have since been fixed, some of them (Waterline defaults to dropping tables unless you have NODE_ENV=production in an env var) are deliberate decisions and hence not "fixable". https://kev.inburke.com/kevin/dont-use-sails-or-waterline/

There's a fair amount of other stuff I would hope to change and that we've just ripped out of our fork.

- If count() isn't implemented in an adapter Waterline will fetch the entire table into memory to count the number of rows.

- Sails by default creates a route for every function in a controller, which makes it easy for an attacker to bypass policies

- blueprints routinely 500 server error based on user input

- https://github.com/balderdashy/waterline/issues/1248

- All SELECT queries on text fields call LOWER() before matching, so all of your indexes also have to match this

- There's a batch insert interface but N connections are established to insert N records... if one of the inserts fails, the behavior of the other inserts is not guaranteed

After the ugly discussion at the OP's link we decided to fork Sails and Waterline and rip out all of the stuff we don't need. I wrote about that here: https://kev.inburke.com/kevin/safely-moving-a-large-shrinkwr...

Re: Status of Sails.js

#20

Post by kevindeasis »

zensavona wrote: post #9
jondubois wrote: post #7

Earlier quoted context omitted.

Node.js is fine. I'm currently contracting for a major company which is using Node.js in production and it's been great. I've worked on Python backends at my previous startup and I can say that Node.js faster to develop with. Linkedin also uses Node.js and they found a 50% increase in development speeds as a result after making the switch a few years ago.

50% increase in development speed after making the switch from what ? I am certainly more productive in Ruby or more recently Elixir than JavaScript on either the client or server.

More productive in the client-tier without using Javascript? I'd like to know how that works.
Post reply on HN