domvm [1] and Mithril [2] promote the same ideas as Backbone, as far as flexibility but with vdom underneath and are far faster than React. domvm is about 2x Mithril performance and both libs are < 20k min. Mithril is more stable and has a much larger userbase, while domvm 1.0 is targeted for 4/1. If anyone is feeling adventurous, feedback and contributions are welcome!
* Disclosure: I'm the author of domvm.
More details if you're interested: https://github.com/leeoniya/domvm/issues/30#issuecomment-193...
Instead of using Backgrid and backbone-validation or alternatives, we've been left creating an in house "tables" approach, and maintaining our own fork of backbone-validation. Neither of those things scale well.
The approach of a small core library with other libraries filling gaps as needed only works when there are good libraries that work well with the small core library :/ For some things its easy to take a "VanillaJS" library and make it work, but for others it really helps to have tight library integration.
Is that the same sort of concept as a "birthday suit"? ( I.e. none at all)
Is there any reason your changes can't be upstreamed?
> 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.
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. Backbone is stable because its ideas are battle-tested and the concepts are all there. People are seeing less usefulness for Marionette / Chaplin / Aurora, and I don't think that's all that bad.
* Disclosure: I'm a core contributor to Backbone.