Backbone walks the line between framework and a collection of modules really well. It gives you just enough to be productive without being overly complex or restrictive. If you go the Backbone route, here's some pointers:
- Make sure you have a system in place for model management, having multiple models around for the same data can be a nightmare
- Backbone views are a bit too simple most of the time, you'll want to at least add a view hierarchy system and lifecycle events/methods.
- You can use the router for as much or as little as you'd like, don't feel like you have to have a new URL for every state in your app.
Backbone walks the line between framework and a collection of modules really well. It gives you just enough to be productive without being overly complex or restrictive. If you go the Backbone route, here's some pointers:
- Make sure you have a system in place for model management, having multiple models around for the same data can be a nightmare
- Backbone views are a bit too simple most of the time, you'll want to at least add a view hierarchy system and lifecycle events/methods.
- You can use the router for as much or as little as you'd like, don't feel like you have to have a new URL for every state in your app.