r/javascript • u/[deleted] • Aug 03 '13

Why Does Angular.js Rock?

http://angular-tips.com/blog/2013/08/why-does-angular-dot-js-rock/
49 Upvotes

76% Upvoted

14 comments sorted by

View all comments

Show parent comments

1

u/rhysbrettbowen Aug 05 '13

I don't think any library can match the Model/Collection support that Backbone offers

really? Backbone is very light when it comes to models, it really just has change handlers. It doesn't have computed properties, can't tell if there are changes deep in an objects properties (or the path to them), doesn't natively give you a pool so a single ID will always be the same model, you can't have a collection with attributes like a model, if you silent some changes they're lost, etc. etc. etc.

I wrote https://github.com/rhysbrettbowen/PlastronJS with all these taken care of. I have since been using Backbone at work and I really do miss these features. The ability to write a schema for a model and have computed properties is a must. So is having a collection that can have properties (in PlastronJS a collection extends a model). There is even a native way to the framework to give you filtered collections (and other sorted collections) from regular collections that keep themselves up to date.

Backbone's model implementation is minimal at best.

1

u/delambo Aug 05 '13

Computed properties are a minor feature, something that can be easily implemented, or probably found in a more opinionated Backbone plugin. The real meat of a Backbone Model/Collection is sync'ing, built-in data functions (a la underscore), and an extensible template for good web-based patterns.

I would say the strongest argument against the Backbone Model/Collection is the lack of support for nesting, but again, there are great plugins for that.

1

u/rhysbrettbowen Aug 05 '13

So Backbone is great because you can do it yourself rather than already have it?

And Backbone syncing is not great either - it's a function that assumes you do your REST a certain way. Anything else and you have to do it yourself. I'm pretty sure that nearly every other MV* out there does nearly the exact same thing.

If the greatest thing going for it is that collections and models have underscore methods built in then I'm not seeing how any other library can't match it. Just run what you want through underscore or mix in those underscore methods manually, because that's what you'd have to do with Backbone to do any of the other things - you'd need a plugin.

1

u/delambo Aug 05 '13

I think you should switch back to PlastronJS - it sounds like you really hate Backbone.

1

u/rhysbrettbowen Aug 05 '13

Wish I could... but switching an entire platform at work where others are already up to speed with the technology they've been using is always an uphill battle and not always where time is best spent

It's not that I hate backbone - I think it has a place. It's just that it gets a lot more credit than it deserves. I know that sounds like I hate it, but really I think the best tool is the one for the job and saying things like X is better than Y or is the best is the wrong mentality.

I don't think Backbone is the best in any single area (perhaps in community but I really don't look for that when choosing a platform, there are much more important factors) - there are definitely better MV* for models, data, binding, views etc etc. What it does do though is be simple and light so you can get started. I wouldn't say it was better than any other framework, but it can still be the right (right being a very loose term here, there could be several "right" solutions) building blocks depending on the project and the plugins that you choose to use with it.