I can only assume that I've finally found a soulmate that just don't like writing TS code.
Like, in my full-time job I'm using 100% TypeScript, but I don't really ENJOY writing in it - that's why in my all side-projects I use good old JavaScript.
I think it's just a personal syntax preference.
But I don't want to answer this for the OP, just added my 2cents, maybe he has similar feeling about it :)
Haha.. There's plenty of us out there, it's probably just that we'd rather do actual stuff than talk about doing it. A bit like Typescript - it doesn't really do anything, it just talks about it.
Joking aside, I generally don't want to get into the debate, because I believe people work differently, and there should be room for doing both things. It's just a bit sad that Typescript is being pushed so hard as if it's the only right way.
> It's just a bit sad that Typescript is being pushed so hard as if it's the only right way.
It's being evangelised as if it has zero downsides, it introduces overhead to what can already be a brittle dependency/build chain - providing questionable levels of actual type safety. This is coming from someone who generally prefers typed languages too, Typescript to me is the exception to that rule.
> Now I use esbuild instead of tsc, and I have the best of both worlds.
I'm interested in this. I know esbuild can compile TypeScript to JS, but that it doesn't serve as an actual typechecker. Without tsc as a dev dependency, do you just rely on your IDE's intellisense to tell you when there's a type error?
I still install tsc, but I don’t actually do the type checking except at release time (and whatever typechecking the IDE provides through the language server).
Like, in my full-time job I'm using 100% TypeScript, but I don't really ENJOY writing in it - that's why in my all side-projects I use good old JavaScript.
I think it's just a personal syntax preference.
But I don't want to answer this for the OP, just added my 2cents, maybe he has similar feeling about it :)