3 ms·
It's not just an hour to learn. There's also the time to set up tools and environment. It's added complexity up front, and that alone is enough to turn people o
by malandrew 15y ago
It's not just an hour to learn. There's also the time to set up tools and environment. It's added complexity up front, and that alone is enough to turn people off because there is nothing so wrong with javascript to warrant the effort.
If you know javascript well and are familiar with it's many gotchas and you know how to use your text editor well with javascript, the coffeescript really doesn't add more than it detracts.
- thenduks 15y agoSo, with something like Tower.js the code is written in coffee to start with (https://github.com/viatropos/tower/tree/master/src https://github.com/viatropos/tower/tree/master/src), but in the repo (and in npm) you'll actually get the resulting JavaScript as well (https://github.com/viatropos/tower/tree/master/lib https://github.com/viatropos/tower/tree/master/lib and https://github.com/viatropos/tower/tree/master/dist https://github.com/viatropos/tower/tree/master/dist). This is generally true of most CS projects. I can't speak specifically to whether or not you can use Tower.js without coffee, just saying don't discount a project because the author wrote it in CS. Spine.js (http://spinejs.com http://spinejs.com) is a great example of what I'm talking about.