Introducing Ampersand.js
blog.andyet.com
Introducing Ampersand.js
1–10 of 83 posts
Re: Introducing Ampersand.js
#2Re: Introducing Ampersand.js
#3Re: Introducing Ampersand.js
#4Good for folks that are used to the node modules philosophy - Seems like a logical extension of the browserify effort (bringing Backbone into the frontend modules system). I dig it.
Re: Introducing Ampersand.js
#5I have to say, with this names, I thought it was a joke for a while...
Re: Introducing Ampersand.js
#6Was just reading this today https://news.ycombinator.com/item?id=7169299
Re: Introducing Ampersand.js
#7Re: Introducing Ampersand.js
#8I have to say, with this names, I thought it was a joke for a while...
same, I was expecting a competitor or add-on functionality for underscore.js
Re: Introducing Ampersand.js
#9Re: Introducing Ampersand.js
#10The post is a little dense, I'll try to summarize: it's basically Backbone split into NPM modules so you can pick & choose. For instance, you want Backbone's collections, but don't want the whole Backbone library, so you `npm install ampersand-collection`. They've setup a registry of recommended modules [1] and you compile with browserify. Good for folks that are used to the node modules philosophy - Seems like a log…
* Views have declarative data bindings for updating your html with model data automatically; out of the box, sensible render and remove methods just work; collection rendering is easy.
* Models have explicitly declared properties and types, as well as evented + cached derived/computed properties. You can access model properties without .get('name') and .set('name', value) and events and things just work.