I understand typescript for big projects and wider teams to keep code self-described etc. I do think that there is an awful lot of extra typing writing TypeScript for small projects for minimal benefit. I could count on one hand the number of bugs I've had in my JS projects due to passing the wrong type to a function. I'm just not a fan of typing a bunch of stuff out twice when I don't need to.
I agree, not a big fan of typescript.
I'm also not a very big fan of static typing, but the person is coming from Java so, Im expecting typescript would be easier transition for him
That's true... I come from a C# background so TypeScript looks very familiar to me. I just appreciate the flexibility and terseness of JS and I'm not sure there are always benefits to type-safety when weighed up against the cost of declaring it. Again it depends. In C# I feel it helps because the JIT or AOT compiler use it to make code, in TypeScript it has no benefit unless I abuse the underlying calls without understanding the implication (then we end up in a premature optimization argument).
I'm not seeking to be argumentative, I feel I learn something from the debate.
Actually types in typescript are just used to provide better tooling (better ide support kindof stuff)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.