The Sad State of the Backbone Ecosystem

Re:The Sad State of the Backbone Ecosystem by Cartwright2 on Tuesday March 08, 2016 @03:14AM (#11244067)

I disagree with the title - I don't think this is a sad state at all. This looks very healthy to me. Backbone clearly had a purpose some years ago and it is unequivocally deprecated now. To me, this is a javascript library aging gracefully and opening the way to newer, better libraries. By removing itself from the list of relevant libraries to choose from in the current year, backbone has helped to reduce decision fatigue.

I hope other Javascript libraries and framework follow this trend until we find a handful of "winner" libraries in the same way that each language has its own "winner" MVC library.

[ Parent | on HN ]

Re:The Sad State of the Backbone Ecosystem by spriggan3 on Tuesday March 08, 2016 @05:14AM (#11244434)

> This looks very healthy to me

The author of the project just like abandoned it, does that sound healthy to you ? Backbone is totally irrelevant.

[ Parent | on HN ]

Re:The Sad State of the Backbone Ecosystem by voltagex_ on Tuesday March 08, 2016 @06:55AM (#11244733)

By what measure?

I'm using Backbone again, courtesy of CartoDB.js [1] and have no interest in chasing whatever React variant was just pushed to GitHub.

(Un)fortunately I'm an enterprise developer and that means staying a decent distance behind whatever the "state of the art" is.

A recent experience with npm/ruby/grunt has put me off it until I have a chance to sit down for a few hours and unpick what exactly it was doing (can anyone recommend a way to simulate an NTLM proxy?)

[1] http://cartodb.com

[ Parent | on HN ]

Re:The Sad State of the Backbone Ecosystem by JustSomeNobody on Tuesday March 08, 2016 @08:35AM (#11245078)

Software can be done.

[ Parent | on HN ]