3 ms·
I'm not quite sure what the point of this is. A scan of the diff doesn't reveal anything particularly interesting being done in Javascript that Coffeescript wou
by cheald 12y ago
I'm not quite sure what the point of this is. A scan of the diff doesn't reveal anything particularly interesting being done in Javascript that Coffeescript would get in the way of. It's fine to argue that Coffeescript gets in your way and prevents you from doing things that you couldn't do otherwise, but at least demonstrate examples to that effect.
Even more perplexingly, there are methods like `merge` in examples.coffee/js which, in the Javascript version, are effectively compiled Coffeescript, and which are less concise than they should be; why does the Javascript version call `Array.prototype.slice.call(arguments)` when arguments is never treated as an array outside of length and subscripting, both of which the arguments object already supports? Coffeescript does it specifically so that using arguments as an array is transparent to the user. Why is it necessary in the Javascript version, when the only effect is the creation of an additional object?
It's somewhat silly to argue for Javascript on the basis of it offering finer control over the code, and then not using that control. If you just don't like Coffeescript, fine, but let that be your argument.