|
|
|
|
|
by aikah
4305 days ago
|
|
Why does this has to be an angular library ? there's no need for that. You could provide a generic js library with a way to opt-in angularjs,that way,your data access layer isnt tied to a presentation framework. Can I use this lib with Backbone or React ? why this fixation on making everything depend on angular ? like jQuery in the past ? are we destined to repeat the same mistakes over and over again in the client js world ? |
|
This is just Angular-specific boilerplate to access window/$window and add/retrieve objects without writing a bunch of low-level services. Backbone and Ember already have these model layers but they come with heavy wrappers and getter/setter methods, and the author said he wanted to keep these as POJO objects (which Angular is loved for) without polluting them with ride-along getter/setter methods.