Backbone is "dying", if you will, because an awful lot has changed in the last five years, not because it was necessarily fundamentally bad - though, of course, it had its limitations.
Too many chefs throw their hat into the ring as it is (especially in JS framework land), a higher bar isn't necessarily bad.
2) If the rubyist comment is 'odd' to you, how are you sure that it's denigrating? as for 'messes' and 'useless', you've divorced them from context:
> Backbone led to messes bigger than jQuery messes, it's full of useless stuff
> What's the point of backbone model? it's useless so one has to use relational.
Your concern is tone-policing?
...and whiskey.
FWIW, it's possible to create messes in Backbone, JQuery, D3, React and plain javascript, if you try hard enough.
> As others have pointed out, having a stable API is a wonderful thing for a vast majority of projects
Well obviously it didn't change the sad state of backbone ecosystem. Having good API to build things upon is more important than the stability of an API. Backbone is dying because the core libs aren't good enough in 2016.