Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've had this debate with a friend who's a big proponent of EmberJS (and to a lesser degree Angular). My friend feels that without one of these libraries you will simply be writing way too much unnecessary boilerplate code for a single-page app of significant size. I personally prefer to rely on small modular dependencies, so Component appeals to me, but I've only played with Ember/Angular a little bit so I don't necessarily know what I'm missing. Can you recommend a set of Components that would provide similar functionality and productivity?


I'm still using backbone.js within our app but a lot of people seem to be using things like:

* https://github.com/component/view for views built on top of reactive for declarative bindings

* https://github.com/component/model for models

* https://github.com/component/router for routing

So what we have so far from these 3 libraries is basically a decomposed backbone with declarative bindings. That will cover 99% of your typical app. I don't find there is too much boilerplate.


Take a look at the Ember examples at http://emberjs.com/. They're doing a lot more with a lot less code. Backbone had its day, but the world is moving on, and a new project that only offers Backbone-equivalent functionality won't garner much interest from me or probably anyone.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: