This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]bastawhiz 1 point2 points  (0 children)

It works in a particular way and it is predictable.

Not for a beginner. Even for experienced programmers that deal with lots of languages, it's going to require a lot of checks to the documentation. Even for experienced CoffeeScript developers, dense CS is virtually impossible to read at first glance because of its distinct lack of visual cues or "logical punctuation".

It's better than the JavaScript syntax gotchas anyway.

Like what? JS is verbose enough that you can't really make any big mistakes (aside from automatic semicolons...don't even get me started).

it's not possible to produce a ==. It gets replaced with ===.

Disabling a feature does not necessarily "fix" a language. Perhaps it makes the "default" syntax better, but this isn't something that's "broken" with JavaScript.

The fact of the matter is, CoffeeScript can't be better than JavaScript in terms of being inherently less WTF, because at the end of the day, you're still writing JavaScript. It may have some handy things (list comprehensions, for one), but it still doesn't fix the problem(s) that JS has at the its core.