Designer News
Where the design community meets.
almost 9 years ago from Jonathan Levy, Product Developer @revealparis
exactly. I would not have hesitated to pick up coffeescript while I was newish to js but my velocity is fast enough now to where it's a hindrance
You indeed cannot use JavaScript -- https://twitter.com/jornvandijk/status/481118703053209600
I hope it lands soon though, all of our projects are in JavaScript. Having to switch to CoffeeScript just to use Studio won't work for us.
Designer News
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
Have feedback?
I have a very strong aversion to CoffeeScript. I know it's often advertised as a simple syntax for JavaScript and something that lets you avoid the "bad parts" of JavaScript.
The thing is, if you really know JavaScript well, CoffeeScript is a barrier. For example, it forces you to think about classes when there are no such things in JavaScript. Prototype-based programming simply doesn't work that way. There's no real inheritance, just object cloning.
CoffeeScript was a deal breaker for me with GitHub's Atom, as well. For simple tasks, sure, I can tolerate it if I really have to. But anything advanced and it's getting in my way instead of letting me get things done. All of my understanding of JavaScript goes out through the window because I keep having to check what it is that my code gets compiled to.
I know there are people who love it, and that's okay. What works for some people doesn't work for others. If CoffeeScript enables you to write your code more efficiently, that's terrific.
I've devoted a lot of time to JavaScript and I know its quirks and behaviours rather well by now. As I'd never really use CoffeeScript anywhere else, I just can't be bothered to learn a new programming language for a tool that works just as well with normal JavaScript. Is that silly?