We've developed (and keep developing) a rather big application in Backbone.js - it holds up and works perfectly.
We are setting a move from it since it lacks in some areas (no POJOs, no nested, manual binding, lots of extra backbone-mini-libs required), but it does hold well at any scale.
I actually work for people who I consider to be good friends. It's just something I tell people of how this industry works and why it's an awesome job.
This is such a bad idea that I had to comment here:
1. Doesn't scale. You do not want to hand pick text all over your site/web-app.
2. It's not semantic.
3. It's very confusing to new people who looks at your code.
4. If you ever change a single char in that sentence, you will have to re-break it yourself.
var getJSON = function(callback) {
// did async work to get the JSON data and now I want to call the callback function, but is it there?
callback && callback(data);
};
getJSON(); // See how I don't care about the result
Love this wish list! Some great points you got there.
About videos: I rather if they'll allow animated gifs instead. Indie developers just don't have enough money to spend on videos and we'll lose to the bigger companies.
We are setting a move from it since it lacks in some areas (no POJOs, no nested, manual binding, lots of extra backbone-mini-libs required), but it does hold well at any scale.
I wouldn't direct new comers to backbone.js anymore, new trends with 10x more contributors wins over anything. I wrote about it being the C++ of JS MVC frameworks (http://berzniz.com/post/66372634868/backbonejs-is-the-c-of-j...)