4 ms·
> We <3 Backbone.js at &yet. It’s brilliantly simple code and it solves many common problems in developing clientside applications. No offense but I completely
by hasenj 12y ago
> We <3 Backbone.js at &yet. It’s brilliantly simple code and it solves many common problems in developing clientside applications.
No offense but I completely disagree. I don't know what problems does backbone solve.
> But we missed the focused simplicity of tiny modules in node-land. We wanted something similar in style and philosophy, but that fully embraced tiny modules, npm, and browserify.
> So we made Ampersand.js, a well-defined approach to combining (get it?) a series of intentionally tiny, and loosely coupled modules for building JS apps.
So .. what is it exactly? a module system for the client side?
RequireJS[0] has already solved this problem.
After reading the first 10 paragraphs, I still have no idea what is this all about.
[0]: http://requirejs.org/ http://requirejs.org/
- rezistik 12y agoCommonJS is far superior to AMD. This is an attempt to rewrite parts of backbone to make it better, one of the main parts of that is making it CommonJS compatible. The other part is simplifying the getters and setters and the way changing properties fires events.
- blktiger 12y agoI think that is debatable. CommonJS is certainly simpler, however it won't work for browser-based javascript unless you wrap it with appropriate tooling. In that respect it's not just inferior to AMD, but it isn't even a viable solution. Not that I'm against CommonJS. It just requires additional tooling to be "superior" so I don't think you should make such a blanket statement.
- rezistik 12y agoBrowserify? Same wrapping as RequireJS would implement I believe, obviously not the 'same' but same level of performance hit and browser based tooling.
- dustingetz 12y agoParent should not have been downvoted and it irritates me that it was 1. hasenhj is correct, Backbone has been superseded for "advanced" webapps for at least two years and should not be used for new webapp development 2. I had the same confusion and question about what exactly ampersand is and what "advanced app" problems it sovles emotional edit: I've used Backbone, Knockout and React in "advanced" (enterprise-scale) production apps, and studied TodoMVC and skimmed the book for Angular and Ember. My original decision to use backbone & knockout in enterprise scale app almost wrecked my first greenfield project, we spent multiple months ripping out Backbone based code. In 2014, Backbone.Model and Backbone.View are very naive ways to approach frontend problems and it is not obvious why until you've been using them a few months. There is an entire ecosystem of blog posts on HN of people attempting to explain why. Any and all of the above dependencies are better than Backbone/Knockout for new webapp development. They of course have the advantage of learning from Backbone, Knockout, YUI, Sencha etc, so it is no surprise that they tackle the hard problems that backbone makes no attempt to solve.