Echo JS 0.11.0

<~>

tracker1 257 days ago. link 6 points
In the end, there is a cost to type checking.  The extent of that cost comes in time and effort to make sure all your interfaces are typed to get the benefit, in some cases this can be a lot of effort.  The risk from bugs saved by type checking isn't always offset of that effort.  In some cases it is a wash.  You do also gain some in refactoring efforts.

It's definitely a mixed bag.  There's also the fact that TS doesn't keep up with pending JS changes.  For long time if you wanted async functions, you needed TS + Babel, which is often painful to configure well, and then try to get webpack's benefits on top.

Personally, I wish that TS was a babel preset, like flow is.  In fact, I really wish that flow would update to use the typescript definitions, which would be a better configuration pairing imho.
xat 257 days ago. link 2 points
To be honest, TypeScript feels more like a hack to me. If you want types then just use a programming language which has types from the ground up and compile it to JavaScript. Either go all the way down or don't do it at all. Feel free to downvote ;)
chris-l 256 days ago. link 1 point
"if you’re not using Visual Studio Code to write JavaScript, you should be"

XD No thanks.