From somebody who used CoffeeScript extensively: I don't think it's a great choice for bigger production projects. The less "noisy" syntax has some very unfortu

From somebody who used CoffeeScript extensively: I don't think it's a great choice for bigger production projects. The less "noisy" syntax has some very unfortunate consequences. For one, it has zero error correction. Almost any random sequence of characters is a valid program so any minor mistake looks at first like it's working and may even pass some tests but looking at the compiled code makes it suddenly obvious that the code is doing something utterly unexpected. Examples include: * Minor spacing mistakes subtly moving code between blocks. * A variable in a nested scope accidentally reusing a name from another scope and merging the variables. * Implicit return generating huge collections that are never used because a function happened to end in a loop. * Random breakages because the value of the last statement in a function sometimes affects the callee even though the author didn't mean to return a meaningful value. * People not setting strict mode because "it's not needed with CoffeeScript" but then introduce bugs where they try to write to readonly properties which silently "succeeds" (does nothing) in sloppy mode. CoffeeScript looks nice and readable but in practice it's almost impossible to decipher what the code actually does.