4 ms·
It's funny how many JS-related projects choose nondescript names like this. Off the top of my head: "processing", "underscore", "node", "backbone", "mylibrary",
by kree10 16y ago
It's funny how many JS-related projects choose nondescript names like this. Off the top of my head: "processing", "underscore", "node", "backbone", "mylibrary", and (maybe the one that started it all) "prototype". I caught myself doing it after I named one of my js libraries "coordinate".
I'm not suggesting "three.js" is a bad name--it's simple, and I'll probably remember it. It's just an interesting naming trend.
- aperiodic 16y agoFYI, processing.js is a javascript re-implementation of Processing[1], which has a much longer pedigree than the others you mention (it was started in 2001). Personally, I've often been annoyed with Processing's generic name, as it can make searching for solutions for specific issues in Processing difficult, unless there happens to be a solution on the Processing fora. [1]: http://processing.org http://processing.org