Re:The Sad State of the Backbone Ecosystem
by strommen on Monday March 07, 2016 @06:47PM
(#11242626)
I guess I see this as a) not surprising, and b) not a problem.
If you're using Backbone in 2016 (like I am), it probably means you want your "framework" to be simple, stable, and customizable. Given those priorities, using a wide variety of plugins doesn't make much sense.
If you want 3rd-party code to do a ton of stuff for you in an opaque way, you're much better off using Angular or Ember.
If you're using Backbone in 2016 (like I am), it probably means you want your "framework" to be simple, stable, and customizable. Given those priorities, using a wide variety of plugins doesn't make much sense.
If you want 3rd-party code to do a ton of stuff for you in an opaque way, you're much better off using Angular or Ember.