|
|
|
|
|
by hitekker
3829 days ago
|
|
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. |
|