4 ms·
Well, I was huge fan of CoffeeScript, so you’ve got me there. I don’t regret a single one of the (many) times I used it though. It made me and the teams I was
by danenania 8y ago
Well, I was huge fan of CoffeeScript, so you’ve got me there. I don’t regret a single one of the (many) times I used it though. It made me and the teams I was part of significantly more productive and allowed us to produce more concise and maintainable code than we could have with plain JS. I feel the same about TypeScript today except honestly the productivity gains are a lot more dramatic.
- Yaggo 8y agoAs a former coffeescript fan, doesn’t the extra “clutter” in typescript syntax bother you? I like CS very much myself. While I can see the benefit of having type system (in certain projects), I just can’t get over the aesthetic/syntax issue.
- true_religion 8y agoFor me, not really. If I want to use type annotation, I need to write the types somewhere in order to communicate it to future readers. I would much rather do it via Typescripts annotations than JSDocs. It's not clutter as it was deemed necessary by the writer (me). If I don't want to use type annotations, I simply don't add them and Typescript does not force you to do so unless you tell it to.
- danenania 8y agoFor me, most of the key CS features that made me reach for it all ended up in ES6. And while I also prefer CS indentation to braces, I don't see that as very important.