Hacker News Reader

Comment by duhruh | Hacker News Reader

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 getting all current developers of Sails libraries to either make their library trails compatible or die. This guy really doesn't like Mike and even though he has some good points on making a new framework it seems there might also be some personal issues driving this decision.

View on HN

Personal or not, our entire company is devoted to making Trails the best damn backend framework for node. We don't distract ourselves with VC-funded side projects, and we don't have a automated bot that closes everyone's issues (see: SailsBot).

Our company lives off consulting around the open-source tools we build and support. That's it.

"We don't distract ourselves with VC-funded side projects". Ouch. These 'low blows' are childish at best. IMO, I wouldn't think a YC backed + VC funded company would be a side project.

It's good that you can be passionate about what you are doing, but it's obvious there are other motivators

EDIT: sp and example motivator -> https://twitter.com/TravisWebbUSA/status/679406525358600192

I'm not saying it's a bad thing man i understand the situation in fact i'm pretty excited to see what Trails has to offer, I was even hoping to make waterlock trails compatible or work on something for Trails. I'm just saying it's important to keep these things upfront, i commend you and your company for taking on this task and like you said before (somewhere i forget) it's refreshing to be transparent about the motivations and issues at hand.

Your language puts Travis's post in the worst possible light, "vendetta", "compatible or die" etc, when in actuality, most Sails.js devs, including myself, up until this post, were unsure about the continuity of the project.

If I were to speculate, I believe this diction has less to do with Travis hating Mike and more to do with the fear of being outmoded, i.e. "We built our library on SailsJS and it would be unthinkable/very difficult to change if SailsJS was subsumed by another project"

Comments on your main library give credence to this fear, such as the one posted by the main dev just recently in the Github issues:

> Waterlock has been struggling recently because of a lack of time from the guys that maintain it. I've tried to do what I can and so have the other guys. But there hasn't been enough going on recently.

Factoring in that Waterlock has 43 open issues since 2014 that have either not been closed or given a label, I can see why there would be uncertainty over this library's future.

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.

I saw this discussion because Travis paid to promote a tweet to it. I'm still not sure what would inspire a person to do such a thing, and clicked to find out why. I'm still no closer to an answer.

Reply on news.ycombinator.com