Earlier quoted context omitted.
"yet our frontend code is reactjs without typescript" I don't blame them. I hate Typescript. Worked on projects at a major gaming company, no typescript necessary.
Of course your opinions are your opinions. However, if the JS build system was actually sane, TS would be the default choice. It's a superset of JS, so saying no typescript necessary is like saying a horse gets me from a to b, no need for cars. TS is objectively better for many use cases and situation if you spend an hour learning it without all the build tooling nonsense getting in the way. It's equivalent to a comp…
I learned it but never saw the need for the extra overhead.
It's full of these situations. And I'd rather just see less code due to "Attention Economy" issues-- the more things to focus on, the less focus each thing receives. It's easier on the big picture, if there's less things going on. TS has a ton of terms and concepts that I just don't need to make my business logic work.
const cat Cat cat = cat
vs.
const cat = cat
dto? iterface? i can define those without typescript. Just plain objects with comments about what they do and what they are.
Anyway, yep it's just my personal opinion of course.
My opinion is basically... I think in some cases there's a desire to make things overly complex, sometimes even as a way to gate keep--
I'm not saying that's what is happening here.
But sometimes I feel that way about Typescript leaking into all of the Javascript ecosystem.