Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Ha! Not necessarily those specific examples, but the overall reaction to it. Here are a couple of other articles which explain the same things:

Section "full of surprises": http://ruoyusun.com/2013/03/17/my-take-on-coffeescript.html

http://ceronman.com/2012/09/17/coffeescript-less-typing-bad-...

And here's an old HN comment of my own which described a few representative difficulties: https://news.ycombinator.com/item?id=4518892

Also, there's no such thing as a global in CoffeeScript (unless you explicitly specify window.xyz), since everything is scoped to the file. And that's the point -- it's ridiculous to have to "look carefully" at all your code to see if functions further down share a variable name inside of them. In JavaScript, you don't need to worry about that because you know "var" scopes each variable to its function, regardless of whether a higher function or global variable uses the same name. In CoffeeScript, you suddenly do have to worry about that, which is fairly insidious and bug-prone behavior.



Hm.. well you may want to use more precise language in the future, because you said you "completely agree" and that it describes "exactly".

So you are saying that none of those particular issues are problems you are having today with CoffeeScript or were problems for most of the year?

In which case, what problems did you have?

Edit: it looks like in another thread you are pointing out some random and unmaintainable code examples that are ambiguous and saying that its hard to know how they will be interpreted by the compiler. Its hard to know how those examples would be interpreted by anyone, or why you would write code like that and create that problem for yourself.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: