I realise I've never worked on a large JS project (only TS). So perhaps I don't really have real-life examples to compare.
I agree the ability to refactor is more related to test coverage (of use cases) than to having types or not.
I just never felt slowed down by TypeScript, and I did when I worked on (even small) projects using only JS because I need to load the "types" or object-structures in my head instead of letting my IDE and type checker do it for me.
I never had to ask myself:
What's the shape of the object this function is expecting?
because in TS you can't get it wrong. My IDE will highlight it in red as I make a mistake.
I only add type annotations where strictly needed, I let type-inference do the work for me.
I don't spend much time writing types.
I'm not sure what's the process/ceremony you mentioned.
Cheers!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I realise I've never worked on a large JS project (only TS). So perhaps I don't really have real-life examples to compare.
I agree the ability to refactor is more related to test coverage (of use cases) than to having types or not.
I just never felt slowed down by TypeScript, and I did when I worked on (even small) projects using only JS because I need to load the "types" or object-structures in my head instead of letting my IDE and type checker do it for me.
I never had to ask myself:
because in TS you can't get it wrong. My IDE will highlight it in red as I make a mistake.
I only add type annotations where strictly needed, I let type-inference do the work for me.
I don't spend much time writing types.
I'm not sure what's the process/ceremony you mentioned.
Cheers!