Yep, the problem is (as I said) - the widespread misunderstanding of what 'TS is a superset of JS' actually means. I've lost count of the number of times I've heard people say that 'all your existing code written in JS will run with no problems in TS, you can just add the types gradually' - and then watching the ensuing chaos.
I've written libraries for JS that some really good TS developers I know have tried to make compatible with TS... they gave up!
TS can certainly be the right tool in some situations, but other situations it actually blunts the power of JS.
Yep, the problem is (as I said) - the widespread misunderstanding of what 'TS is a superset of JS' actually means. I've lost count of the number of times I've heard people say that 'all your existing code written in JS will run with no problems in TS, you can just add the types gradually' - and then watching the ensuing chaos.
I've written libraries for JS that some really good TS developers I know have tried to make compatible with TS... they gave up!
TS can certainly be the right tool in some situations, but other situations it actually blunts the power of JS.
The misunderstanding is people think by copy and paste think will work
No, by superset it means the compiler understand JS syntax
it has nothing to do with the effort of the developer, it is not about the developer!