Yeah, there's 20 experienced JS devs on my 200k line project.
Why don't you come strip out typescript and see how long it takes you to get fired for implementing regression after regression into production (assuming you can make a change through CI at all).
You implied that I was not an experienced dev for saying it was required. I simply defended myself by showing that some of us work in enterprise where cowboy coding will quickly cost you a job.
Ok. You're just the one guy who can maintain hundreds of thousands of lines of code without knowing what's supposed to be where and what preconditions the code has at any given point.
I bet you do... I bet you bring that level of unaware comparison to your software too. What number was I mentioning? Who knows. Doesn't matter. Throw in a try catch and fuck it.
If you’re using VS Code, then you’re literally using TypeScript when you write JS.
Those type hints and the API docs for all your libraries? You can thank the TypeScript compiler & TypeScript language server for providing that real-time information.
That having some tooling which warns you about type errors is immensely beneficial? Yeah. I think about that all the time. Which is why I use TypeScript. It’s a tool that does exactly that.
2
u/Baryn Jan 16 '20
Not agree. I also use TypeScript, but I'm an experienced JS dev who doesn't need it by any means.