4 ms·
Where I work, we moved the project I work on to CoffeeScript about a year ago, and I've been using it ever since. Putting syntactic sugar aside, while some thi
by crazygringo 14y ago
Where I work, we moved the project I work on to CoffeeScript about a year ago, and I've been using it ever since.
Putting syntactic sugar aside, while some things are very welcome (list comprehensions, ===, ?), there are two main reasons why I would be wary of using CoffeeScript again:
1. Complete lack of documentation for syntax. Because there are basically no more braces and parentheses, CoffeeScript just tries to guess what you're doing, as far as I can tell, based on a bunch of internal heuristics. Unfortunately, there's no way for me to learn how to write parseable code without constantly pasting into the coffeescript.org site, and seeing if CoffeeScript understands it or not. This is the first language I've ever used where the syntax rules are essentially unknowable, and a lot of time gets wasted trying to discover them through trial and error.
2. Unexpected side effects. For example, functions return the last evaluated value by default. If you're using $.each(), and your function's last line is something that returns false (like a separate function you call), then your $.each() loop will terminate unexpectedly early, since jQuery does that when it receives a false. So CoffeeScript isn't just a wrapper around JavaScript, but it really changes its behavior. Another example: CoffeeScript gets rid of function hoisting. A significant JavaScript feature, completely gone.
I personally am slower to code in CoffeeScript, because I know JavaScript 100% inside and out, but with CoffeeScript that isn't really possible, because so much of its implementation is undocumented. I mean, many times you're forced to end a line with a backslash in order to continue it, and even the existence of that necessary feature isn't mentioned once in the docs.
But a lot of people seem to love the syntax, and that seems to outweigh the negatives for them. I personally don't find JavaScript that ugly, but coding in a language I can't ever fully understand gives me a huge headache.
- latchkey 14y ago#1 I agree, making stuff optional was a bad design decision. It encourages people to write code in different ways and makes for unreadable messes if coworkers aren't religious about how they format things or they do things differently than you do. #2 has definitely bitten me, but I see that less of a failure of CS and more of a failure of the design of $.each(). The case is pretty well documented in CS though... the last code line is 'return'ed... if your code unexpectedly returns false, then really you are just bitten by the design of $.each().
- tolmasky 14y agoYour only other options for early termination of $.each are pretty cumbersome. On the one hand you can bend over backwards to pass in the "should continue" flag "by reference". In C you might pass in bool * should_continue, then do *should_continue = false. In JavaScript you'd have to wrap that in another variable, like flags.should_continue = false, which is less elegant in my opinion. Alternatively, I've seen libraries abuse throw to achieve this, which I also don't like (and I believe has pretty bad performance characteristics, but I can't remember for sure).
- latchkey 14y ago... or you can write it in CS with a for loop which cleans up the syntax quite a bit... or it might be possible to reduce your input first so that you are only iterating over the things you actually want to iterate over...
- tolmasky 14y ago"...or you can write it in CS with a for loop which cleans up the syntax quite a bit" For each loops are great, but there is certainly value in having $.each be a function as well as a statement. For example, if you want to pass it to another function in more functional style programming: do_something($.each); "or it might be possible to reduce your input first so that you are only iterating over the things you actually want to iterate over..." It seems you don't understand the point of returning false from $.each, it is not to filter, it is to stop early. For example, if you are doing a linear search for something, it is reasonable to want to stop after you find it. There is no way to "iterate over the things you actually want to iterate over".
- latchkey 14y agoI think you're stretching here. Passing $.each to a function makes no sense when it is effectively a global anyway. Please give me a real world example of why you would do something like that (not in the functional aspect, that I understand... I am talking specifically about $.each). I also wouldn't use something called $.each to do a linear search. I'd use underscore.js _.find(), which has a sane api, you return true when you want to stop. This thing I'm looking for has been found. Array.forEach and _.each() chose not to support returning false. I can only assume that is @jashkenas being wise.
- lowboy 14y agoPardon? The coffeescript site has pretty comprehensive info that describes the syntax. If you don't find a specific example on the site, "it's just Javascript" has rung true for me in almost every case. Yes, there is a learning curve and it does things slightly differently. The implicit return value is just something you read once and then integrate. True, function hoisting is lost in cs, but that has never been a problem for me.
- crazygringo 14y agoJust three completely undocumented syntax examples... Mapping values in an object: {a, b} = c Backslash to continue lines: a = long_variable_name \ + other_long variable name Switch statements without a parameter: switch when function_that_needs_to_return_true stuff But the bigger problem is just having no idea how things will parse. For example, this works: a = b + c But this doesn't: a = b + c And then this works: switch a when b, c, d e() But this doesn't (a multi-line form you might want to use if the variable names were really long): switch a when b, c, d e() And this doesn't: switch a when b when c when d e() After trial-and-error, you discover it has to be this, with a seemingly random backslashes: switch a when b, \ c, \ d e() I could go on and on -- but you get the point. The whole language is only discoverable via trial and error. None of this is documented. (Apologies for taking up so much vertical space of the comments!!)
- lowboy 14y ago1) Destructuring assignment: http://coffeescript.org/#destructuring http://coffeescript.org/#destructuring (although they lack an object example). 2) This has to do with the unary plus operator more than just cs - since +varname is an expression, it treats it as such. Fair complaint - I've never run into that. Also, this works just fine if you put the plus on the end of the first line: a = long_var_name + hey_another_var 3) When would you use those? 4+5) Are cases of the unary operator in 2) 6-10) Sure, this is limiting if you want to write switch statements like that. I feel that your coding style is different, or that you're listing edge cases to be contrarian. Coffeescript has a much smaller range of syntax deviations but that's part of what allows it to be so brief and clean.
- jlongster 14y agoCoffeeScript can't really claim that "it's just javascript" either. I'd have to figure out how to hook up the CoffeeScript compiler into every single one of my workflows where I use javascript. For example, I use swank (https://github.com/swank-js/swank-js https://github.com/swank-js/swank-js) to send javascript to the current page in my browser from Emacs. I couldn't live without it. I'd have to figure out how to dynamically compile it, and I'm not sure if there's any restrictions with piece-meal compilation. It's definitely a separate community and I'd lose out on lots of good tools if I had to use it. I'm glad nobody wants to use it where I work.
- lowboy 14y ago"It's just javascript" !== "You don't have to change your workflow at all"
- icandoitbetter 14y agoPiecemeal compilation: // beginning of file Coffeescript = require('coffee-script'); // compilation Coffeescript.compile(line, {bare: true}); e.g. var f = eval(Coffeescript.compile("(x) -> x + 1", {bare: true})); f(1) // ==> true
- pooriaazimi 14y agoWhy and how could function hoisting be useful? (Genuine question, not an snarky comment) Edit: Huh! I thought you meant "variable hoisting", which is the most evil language feature that's ever bitten me! This is an introduction to "function hoisting": http://elegantcode.com/2011/03/24/basic-javascript-part-12-function-hoisting/ http://elegantcode.com/2011/03/24/basic-javascript-part-12-f... - Very very interesting.
- jarek-foksa 14y agoI always felt that function hoisting is harming code readability. I prefer reading the code from top to bottom, I don't want to stuble upon functions that were not declared before. If I recall correctly the main reason why this feature is not supported by CoffeeScript is because of some awkward IE bug though.
- jashkenas 14y agoThe main reason is what you say -- it harms readability. Much better to have functions behave like any other value, like any other variable -- and only be usable after they've been created.
- tripzilch 14y agoI agree, although I also see some usefulness: If your inner function names are sufficiently descriptive, you can write the high-level behaviour of the outer function at the top, first to be read, to get a quick overview of what it does. Then declare the inner functions below that (this also requires that the inner functions must not have surprising side-effects). I've never seen or tried out code like that in practice, but it seems like it could work.
- johnx123-up 14y agoThis is exactly my position. I have used CoffeeScript in 3-projects and moved back to JavaScript. The biggest problem for me is the readability. JavaScript has braces and good readability, IMHO. YMMV.