The example in "Ambiguous Code" is ridiculous - if you write CoffeeScript like that then you have much bigger problems. Also, the part in "Classes Are an Illusi

The example in "Ambiguous Code" is ridiculous - if you write CoffeeScript like that then you have much bigger problems. Also, the part in "Classes Are an Illusion" totally fails to mention the fat arrow `=>`, which solves the main issue the author raises. However, this part I completely agree with: > Realistically, the issues I have raised with CoffeeScript don’t come up every day. Ultimately though, they are enough to say we need something better. I hope to share some thoughts soon on what such a solution might look like. CoffeeScript isn't perfect and we should always be looking for better solutions. So I'm glad that the author wants to add to the discussion. While CoffeeScript isn't the answer, it's probably the best answer we have so far,