1–10 of 78 posts
My first choice at the moment is batman.js which is very similar to rails (where I'm coming from), but I'm worried that it's not so developed like others (at least checking the github repo)
I'm a junior developer (if that), and I've found the strong opinions and conventions of Ember very refreshing.
where's react?
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.
Officially adopting a technology like that is pretty rare, and I guessed Angular had started to achieve a level of adoption that would make it the most worthwhile to invest in.
I also wrote more about how I think it's going to be huge, which I admit sounds best if you already love angular :) http://ionicframework.com/blog/angularjs-will-be-huge/
where's react?
also DocPad for static sites with more content than code.