i don’t understand the hate for TS. after the initial learning curve, it has only made my life easier. i can’t imagine making a large refactor on a JS code base - the fear of breaking some unknown contract keeps me up at night
I dabbled in JS for 25 years. Last year I had reason to write some TS. What a breath of fresh air that was! I doubt I’d start a new project in bare JS now.
Because there are thousands of settings that have to be considered for the transport to work correctly. And for every packet out there, these settings need to be correct. Then debugging is also difficult, because stepping through the TS code doesn't always work as expected.
You only need to get those settings right once, and only at build time.
I won't defend the mess that are web build systems, but your assertion that things need to be right "for every packet" is false. And while I've had no trouble debugging TS code, you could always just debug the generated unminified JavaScript instead.
I meant package, not packet. And no , you don't have to get it right only once. I started a svelte app with TS, and when I tried to add Prisma, it took me a lot of time and research to get the settings correct, so everything would work out. And I wasn't alone. There were numerous posts, and issues on GH about that same thing, so I was far from alone.
And debugging JS is one way of doing things. But when I write code, I want to debug that code. Not the transpired stuff. It just adds a layer of annoying complexity, that otherwise wouldn't be there.
i don’t understand the hate for TS. after the initial learning curve, it has only made my life easier. i can’t imagine making a large refactor on a JS code base - the fear of breaking some unknown contract keeps me up at night