Downloaded 80 times
Uploaded byDagfinn Reiersøl
Backbone.js versus AngularJS
The document discusses a need for a framework to build a useful object model without the requirement for explicit event handlers for form interactions. It outlines experiences with backbone.js, rivets.js, and angularjs, highlighting both advantages such as easy two-way data binding and disadvantages including poor documentation and a sprawling codebase. The insights shared reflect a quest for a more efficient and supportive frontend development environment.
Backbone.js versus AngularJS
- 2. Wanted: a frameworkthat: Allows me to build a useful object model Doesn’t require me to write explicit event handlers to update the Model from form inputs Satifies frontend developers
- 3. Tried this Proof of concept: Basic form for editing an object’s attributes Very limited universe explored Backbone.js with Rivets.js (because it worked!) AngularJS
- 4. Not married toa framework (yet)
- 5. Why I likedAngularJS ”Frontend friendly” Simpler code in the proof of concept Easy, natural two-way data binding Model is a plain JavaScript object Dependency injection system
- 6. Problems with Angular Some things just don’t work??
- 7. Problems with Angular Some things just don’t work?? ”Codebase appears to be fairly sprawling and not very modular.”
- 8. Problems with Angular Some things just don’t work?? ”Codebase appears to be fairly sprawling and not very modular.” ”Angularjs documentation is absolutely abysmal. They are truly awful. I can't say enough how terribly terribly terrible they are at explaining themselves.”