Re:Tower.js - JavaScript Framework for Node.js modeled after...
by malandrew on Monday February 27, 2012 @08:55PM
(#3641469)
That's not the point of his comment. It's labeled javascript when it is actually coffeescript. Call it tower.coffee, not tower.js.
If I can't fork and contribute to the project in javascript, but instead have to set up my environment for coffee script to contribute, then it's not javascript.
This isn't just about readability and comprehension, it's about contribution as well.
If the compiled javascript is bundled in there and I can read it, fair enough. If you can't accept patches and code contributions in javascript, then that's not javascript.
If I can't fork and contribute to the project in javascript, but instead have to set up my environment for coffee script to contribute, then it's not javascript.
This isn't just about readability and comprehension, it's about contribution as well.
If the compiled javascript is bundled in there and I can read it, fair enough. If you can't accept patches and code contributions in javascript, then that's not javascript.