A friend of mine, who isn’t a programmer, recently wrote to me with a question:
What does .JS mean on the end of a tool like Angular or Backbone?
However, if you start thinking about where the naming convention comes from, and why it’s popular, then you might suspect that there’s a story here.
File name-based framework naming
The obvious explanation for the -.js suffix is that the frameworks are taking their names from their source files:
AngularJS then, simply takes its name from the file name
angular.js. So what’s the big deal? The big deal isn’t that the framework name comes from the file name. The big deal is that there’s only one file. If it were some other programming language, there’d be thousands.
The problem with it being so easy to create a little framework is neatly summed up by James Ward, in this ‘sign at the W3C headquarters’:
Letting a hundred flowers blossom and a hundred schools of thought contend is the policy for promoting progress in the arts and the sciences and a flourishing socialist culture in our land.
Hollywood naming disambiguation
Short but happy lives