delambo

If you have code duplication/DRY problems, then Backbone is not your problem. You need to abstract common functionality and add mixins to Backbone.View.prototype.

In every backbone project that I have developed, the set of View mixins that I create are very specific to each project and the custom UI/UX I build. It would be a useless exercise to abstract all of my View mixins into some kind of opinionated framework, because I know my next project is going to look and behave differently.

That said, if you are working on a large project with some simple UIs/UXs and need some simple data binding, then you may want to check out an "ambitious" framework like ember.js. Backbone is a library that helps you organize large projects with a lot of complex and custom UI/UX.

How does this work with minified/obfuscated production code? Some of the other comments suggest that proxino is listening to and logs on 'window.onerror'. If that is the case, I don't think you can get stack traces in all browsers, and the line number for a minified file will alway be 1.

I agree that this is an issue, and I plan on working to remove this restriction in the future.

https://github.com/NYTimes/ice/issues/2

Out of the box, you can do this in a very basic way. If you check out the tinymce demo version, you will see two buttons for accepting and rejecting changes which use ice's API (`acceptChange`, `rejectChange`) to modify the nodes.

We wanted the focus for ice to be on change tracking only so we intentionally left out track changes presentation/interaction details. I think there is a lot of potential for good UI/UX tools to be built for the track changes that ice produces and I would love to feature them in the project wiki.

Coming from a Java workshop, I have noticed the exact opposite - the majority of Java developers I have worked with are unwilling to touch or experiment with anything other than Java, even languages on the JVM like Scala; alternatively, I have noticed python developers are much more open and agile when it comes to moving in and out of other languages.

Does anyone miss the pre-facebook days of online social networking where people mostly used aliases other than their real names?

Back then, we actually networked and found like-minded people or new friends through the tool. Now, we wait until we meet someone in real life, then find and friend them on the tool.

If this solves your problem, then you probably didn't need MVC in the first place. But this doesn't necessarily decouple you from the DOM, and it sounds like all of the code that works with these models is a bunch of jQuery callbacks hooked into the DOM. Is that right?

If so, and your project is sizable, then an MVC, like backbone.js, could be beneficial.

I can't comment on the dev activity for any of these tools, but I do have experience with lab.js and require.js.

From what I have seen, the functionality of head.js looks like a subset of lab.js. Lab.js has a richer API with queueing and waiting. Require.js is a whole different beast - it revolves around the definition of modules (module pattern) and the scripts required to pull down to organize modules. There are a lot of tools in require.js that help with ordering the execution of loaded scripts, pulling down files as text (can't do this in lab.js), and optimizing (compiling modules into one big uglified file).

They are all good tools, but different - pick the best one suited for your project.