3 ms·
> The first time I saw CoffeeScript I immediately realized, oh, fuck yes, this is obviously better, and switched over to it immediately. I was productive with i
by mattdw 13y ago
> The first time I saw CoffeeScript I immediately realized, oh, fuck yes, this is obviously better, and switched over to it immediately. I was productive with it instantly.
Which is fine for you. But I tried it for a project then ditched it, because it didn't justify the extra tooling required in my development pipeline, and because there are ambiguities and inconsistencies in the syntax and the language, and yes, occasionally it's actually worse than Javascript.
Which is only to say that not everyone fits into a "doesn't know CoffeeScript"/"loves CoffeeScript" dichotomy.
- gfodor 13y agoThe point wasn't that everyone should use it. The point was that it was trivial to pick up and use so I'm often surprised when people complain about how difficult it is to read. If I handed you a piece of CoffeeScript and you literally had never read the docs, but are a competent programmer who knows Javascript well, it'd be surprising if you couldn't just read it as-is and know what it's doing since you know it's just an alternative syntax for javascript.
- cnp 13y agoI don't mean to sound dense, but who isn't using some kind of build system these days with their JavaScript? "Extra Tooling" really is quite trivial given the general de-facto standards that are now in place. As far as the ambiguities and inconsistencies go, that I can understand.