The learning curve for CoffeeScript is so low and the benefits so high that it's a smart decision to use it. You're not giving up Javascript, the number one rule of CoffeeScript is that CoffeeScript is Javascript. I don't think anyone expects you to learn CoffeeScript before Javascript. CoffeeScript is basically a tool you pick up in an afternoon after you have spent the time needed to understand and wield Javascript.
You're not giving up Javascript, the number one rule of CoffeeScript is that CoffeeScript is Javascript.
What does this even mean?
CS has different syntax. You cannot take random CS code and drop it into a JS app and run it. CS needs to first be converted into JS, which wouldn't be necessary if CS were JS.
Comments
The learning curve for CoffeeScript is so low and the benefits so high that it's a smart decision to use it. You're not giving up Javascript, the number one rule of CoffeeScript is that CoffeeScript is Javascript. I don't think anyone expects you to learn CoffeeScript before Javascript. CoffeeScript is basically a tool you pick up in an afternoon after you have spent the time needed to understand and wield Javascript.
You're not giving up Javascript, the number one rule of CoffeeScript is that CoffeeScript is Javascript.
What does this even mean?
CS has different syntax. You cannot take random CS code and drop it into a JS app and run it. CS needs to first be converted into JS, which wouldn't be necessary if CS were JS.
The point is that the semantics of CS are the same as javascript.
There is no run-time interpretation, libraries or magic like in some other to-JS languages.
You still have prototypes, function scope, closures, etc. but with a (arguably) nicer and cleaner syntax.