3 ms·
That's a good question! I think we'll ask the same question about Typescript in the future; I've integrated into a UI project I work with other people, to make
by heldrida 8y ago
That's a good question!
I think we'll ask the same question about Typescript in the future; I've integrated into a UI project I work with other people, to make one of our devs happy, but I won't use it myself.
A few years ago I remember having one colleague who wanted to write in CoffeeScript but at that time we didn't know how to interoperate with JS, I believe? Or our tooling or knowledge wasn't the best, so we decided not to let him write CoffeeScript; From time to time I hear from that team and the project is still alive - luckily they don't have to support CoffeeScript.
I think you should use whatever makes you happy, for your own projects, but in a team, have in mind others and the future.
- woah 8y agoTypescript gives real benefits with type checking vs CoffeeScript which just looks sort of like Ruby. It’s hard for me to imagine why someone would prefer endless “Cannot read property foo of undefined” runtime errors in normal Javascript over Typescript’s in-line linting of those errors.