Hacker News new | ask | show | jobs
by tantalor 4695 days ago
Your answer to "why it rocks" is "data binding." Why does this seem like an important feature to you? What problem does it solve?
2 comments

Support for two-way binding significantly speeds up development time when compared to the old way of doing things because so much of frontend development consists of shuttling JS objects to the document and returning user input to those objects. It is night and day using one of these frameworks when compared to the old favorites (ExtJS, Closure Library, Dojo).
Yes it speeds up, but significantly ? Like in Backbone, some lines of code and if you build a small "Framework / Function-Set" on top of backbone Marionette (~10 Lines of Code), you have nearly the same feature.

Did somebody really looked at Ember and its Ember-Data and the missing features that you need when you program a RESTful application? E.g. Server Errors. Ember "Frontend" is nice, but Ember "Backend" is (in my mind) not production ready.

And only for a little two Way Binding 800 KB of Code? ;-) I think Ember has more to give.

I have the same feeling -- I can't say I've ever needed that feature. I think it's /neat/, but it's not neat enough that I couldn't do without it.