Short answer:
It is worth it if you want me on the team. I refuse to work with anyone who throws out TS for JS in 2023.
Slightly longer answer:
I have said a number of times
"Javascript is a simple version of Java in the same way as a bike with one wheel is a simpler version of an ordinary bike."
The same can be said about JS and TS.
If you want to do any serious work you go for the serious thing even if it means occasional adjustment of brakes and gears, or in Typescripts case, sometimes figuring out something.If anybody suggest to use Javascript today I won't take them seriously.
i) I have used Typeescript since 2017. For some reason I don't have these problems and never had.
ii) Yes, some libraries are poorly documented, that is for me a reason to prove why I am a software engineer by either figuring it out, complain until they fix it or even better use my gut feeling and use some libraries that aren't stuck 10 years ago.
iii) Error messages can be hard, but compared to debugging the mess that happens without typing it isn't hard at all.
iv) Have someone look at your project setup.
And before someone says I don't know Javascript: I wrote my first javascript application (OK ECMAScript since it was in Adobes SVG plugin), which was a working map, dynamically updated based on GPS position, back in the spring of 2005, that is half a year or so before Google Maps and years before most people took Javascript seriously so I should be qualified to have opinings. Yes, it wasn't production quality, but I built the logic more or less alone in 5 months in between other school work.
It is worth it if you want me on the team. I refuse to work with anyone who throws out TS for JS in 2023.
Slightly longer answer:
I have said a number of times
The same can be said about JS and TS. If you want to do any serious work you go for the serious thing even if it means occasional adjustment of brakes and gears, or in Typescripts case, sometimes figuring out something.If anybody suggest to use Javascript today I won't take them seriously.
i) I have used Typeescript since 2017. For some reason I don't have these problems and never had.
ii) Yes, some libraries are poorly documented, that is for me a reason to prove why I am a software engineer by either figuring it out, complain until they fix it or even better use my gut feeling and use some libraries that aren't stuck 10 years ago.
iii) Error messages can be hard, but compared to debugging the mess that happens without typing it isn't hard at all.
iv) Have someone look at your project setup.
And before someone says I don't know Javascript: I wrote my first javascript application (OK ECMAScript since it was in Adobes SVG plugin), which was a working map, dynamically updated based on GPS position, back in the spring of 2005, that is half a year or so before Google Maps and years before most people took Javascript seriously so I should be qualified to have opinings. Yes, it wasn't production quality, but I built the logic more or less alone in 5 months in between other school work.