In my previous post about Backbone I chose not to go into details. Apparently, even though appreciated, the bottom line wasn’t enough. People expect explanations… So I decided to write another post that better explains why I think Backbone should be avoided as infrastructure for web applications (not web sites). However, since I didn’t want ...
Backbone.js is a pointless piece of code! If you need a framework for your web application, do yourself a favor and stay away. You’re probably wondering about how this can be true, right? I mean, after all, there must be a reason behind Backbone’s success… Well, of course there’s a reason. It is one that ...
Building complex applications with JavaScript isn’t a straightforward task because the language has no standard mechanism for creating libraries. CommonJS module specification suggests a way in which libraries (modules) should be written “in order to be interoperable among a class of module systems that can be both client and server side”. Node implements a similar system that makes ...
In my post about Node modules I demonstrate the usage of require() and exports without going into detail. Structuring a Node deployment can be tricky, mostly because there’s more than one way to organize modules in the file system (particularly when working with npm, the de-facto package management tool for Node). Knowing how require() and exports work is important, ...
