Re:AngularJS from an Ember.js perspective
by epidemian on Friday November 22, 2013 @08:29AM
(#6780552)
But it's cumbersome to have to change lots of code just because a property of some object became computed instead of directly stored (or vice versa). And it's unfeasible to do so if you're developing a library (for external usage, or internal usage within a company)... you can't just go and fix all the code that used it.
[ Parent
| on HN ]
There are no comments on this comment yet.