The actual landing page is http://ampersandjs.com (linked in the first sentence of the blog post) and has plenty of technical content like the user manual/guides you wanted (http://ampersandjs.com/learn) and api docs (http://ampersandjs.com/docs).
The actual landing page is http://ampersandjs.com (linked in the first sentence of the blog post) and has plenty of technical content like the user manual/guides you wanted (http://ampersandjs.com/learn) and api docs (http://ampersandjs.com/docs).
I don't know what that means, and the reasons for it are "simplicity of tiny modules and npm dependency," which are not exactly convincing by itself, as I can do that just fine with plain Browserify. Then, going to the "Learn" page I get my hands busy.. with something I know nothing about.
This is heavily marketed towards Backbone users, I'm guessing.
You're right that it's basically for Backbone users:
> We <3 Backbone.js at &yet. It’s brilliantly simple and solves many common problems in developing clientside applications.
> But we missed the focused simplicity of tiny modules in node-land.
Read as: "This is like Backbone.js (almost a forked Backbone.js) but better." (better from some perspective, at least)