@playest Great point, a language shouldn't get in the way of what you are trying to do. That might be what some of the complaints about TypeScript have been, but if you really learn how to write TS efficiently (something I'm still trying to learn) then it's not a problem.

@stephenadams @playest I think one of the reasons that some devs struggle with #typescript is that they start with the wrong perspective. Once I started thinking about it as "shape definition" on top of #javascript, it clicked for me.
https://chrlschn.dev/blog/2023/09/typescript-is-not-a-programming-language/

@chrlschn @playest Do you think that is because a lot of TypeScript users are from JS backgrounds? The TS users who come from a C# background find it easier to work with. And the problem is that there's not enough good material out there about writing good typescript and not just writing React with TypeScript, which I see a lot of.

@stephenadams @chrlschn I don't know about the background thing. I think it's mostly a personal preference. I started with #PHP 4 (no types) and #python and with both I spend a lot of time being not sure about what exactly was the input of function X. When I tried java for the first time I was amazed that you could basically do "Ctrl + space assisted coding". I have loved everything that can help me be sure of what is a variable since then (and more generally what helps reduce my mental load)...