Live data from Hacker News

CoffeeScript is not a language worth learning

github.com

121–130 of 132 posts

Re: CoffeeScript is not a language worth learning

#121

I'm starting to feel like anyone who has a negative opinion of CoffeeScript should prefix their statements with "I've spent the last M months writing code in CoffeeScript for H hours a day and these are my specific issues with it." Otherwise, these endless discussions of JavaScript vs. CoffeeScript really aren't productive. If you haven't spent time with actual coding in it, then you probably don't have as well forme…

"I've spent the last M months writing code in CoffeeScript for H hours a day and these are my specific issues with it."

Only if we add months spent writing in JavaScript N hours a day too. Bonus for Python and Ruby.

Re: CoffeeScript is not a language worth learning

#122
post #77

Earlier quoted context omitted.

Didn't read the whole thing, nope. But the title says "CoffeeScript is not worth learning".

But the title says "CoffeeScript is not worth learning". No, it says "it's not a language worth learning". The author's point is that CoffeeScript is not a language, but a tool for JavaScript.

I think it's quite obvious the title is deliberately misleading to get more people to read it.

Re: CoffeeScript is not a language worth learning

#123
post #122

Earlier quoted context omitted.

But the title says "CoffeeScript is not worth learning". No, it says "it's not a language worth learning". The author's point is that CoffeeScript is not a language, but a tool for JavaScript.

I think it's quite obvious the title is deliberately misleading to get more people to read it.

Sure, but that doesn't excuse people from commenting without reading it.

Re: CoffeeScript is not a language worth learning

#125

I don't the fact that CoffeeScript can't be debugged until browsers support it. JavaScript errors are bad enough, but until I can get a CoffeeScript source line number in an error I simply refuse.

https://github.com/playframework/Play20/wiki/AssetsCoffeeScr...

Re: CoffeeScript is not a language worth learning

#127
post #20

TL;DR: Coffeescript should be seen as a way to enforce good Javascript style, and as such it does a decent job. That's an interesting and very defensible PoV. However, even considered as such, it has some serious warts: * It has no clearly-defined semantics: it's an accretion of rewriting tricks, and as such, it's often very hard to predict how two tricks will interact together, especially when they involve indentati…

From the coffeescript website: CoffeeScript is a little language that compiles into JavaScript. Underneath all those awkward braces and semicolons, JavaScript has always had a gorgeous object model at its heart. CoffeeScript is an attempt to expose the good parts of JavaScript in a simple way. Coffeescript has never presented itself otherwise. What causes the confusion is pointless discussions about semantics and peo…

The technical term for what CoffeeScript is doing — a compiler that doesn't need a global view of the program and does local source transformations — is a transpiler.

Re: CoffeeScript is not a language worth learning

#128

I taught a new programmer in my department JavaScript and CoffeeScript. Yesterday he told me he saw Notch coding a 2d version of minecraft in Java at a hackaton online, and how weird is the difference between CoffeeScript and Java. Maybe for us there's nothing new in CoffeeScript. Heck, the patterns of programming in javascript, callbacks, functional programming, prototypes, closures, the context of this -- for him i…

So I'm going to learn either JavaScript or CoffeeScript over January. I have some experience in VisualBasic (took a high school programming class about four years ago). Which one should I learn?

JS first, and be sure to use this excellent guide: http://eloquentjavascript.net

It really covers the how and why of JS in a way that will make your understanding sharper.

Re: CoffeeScript is not a language worth learning

#130
post #125

I don't the fact that CoffeeScript can't be debugged until browsers support it. JavaScript errors are bad enough, but until I can get a CoffeeScript source line number in an error I simply refuse.

https://github.com/playframework/Play20/wiki/AssetsCoffeeScr...

Those are just compile errors, though. As far as I know, it's up to the runtime host (WebKit, Firefox, etc.) to implement support for CoffeeScript dbeugging, and that's still in the works.
Post reply on HN