>Not saying it's your case, but I noticed that a lot of people who hate TS like to use techniques and patterns that are usually considered bad practices, which often trigger errors in TS. Mutating an object to add a new property, mutating an array to add an element of a different type, processing apples and oranges in the same function without using generics or the correct union type, etc. Code works but TS doesn't like it and forces them to rewrite it properly and it feels like a hassle with no benefits.
Not sure, people who like TS are usually for large corporate projects with OOP background. Most functional lispish type developer would be fine just using ES6 and above.
Not saying it's your case, but I noticed that a lot of people who hate TS like to use techniques and patterns that are usually considered bad practices, which often trigger errors in TS. For examples, mutating an object to add a new property, mutating an array to add an element of a different type, etc.
I also noticed that lot of people who don't like TS think they need to type everything (every variable, every function's return... which is obviously a hassle) instead of relying on types inference. There is usually very little to type in TS (compared to Java or C# for example). The two main things are the parameters of your named functions and your external data (i.e. the fetch responses). Almost everything else can be inferred.
A last category of issues I see with a lot of people who hate TS is related to generics. They do everything they can to avoid using generics and they get very frustrated to not be able to reuse functions with arguments of different types. So instead they hack some workarounds together to avoid TS errors (which makes any future modification or refactoring even worse), usually by first defining the parameter as an union of types and then inserting @ts-ignore everywhere inside the function where TS still shows errors. Or they just copy/paste the function and change the function signature.