> I don’t want to touch TypeScript stuff with a ten foot pole
Why not? Is it because you need to change the code?
No, I’m just extremely averse to anything to do with JS/TS. The amount of bloat is insane and there’s a new supply chain attack every day at this point. Definition of a tire fire.
Yup - IMO it’s just the wrong tool for the job.
Glad I am not the only one who sees this. The immaturity of the JS/TS ecosystem has only delivered a range of issues (too many to list here) and the negatives significantly outweigh the positives.
> Is it because you need to change the code?
Indeed! It would be difficult to deliberately design a more long-term-TCO-destructive ecosystem.
Effectively everything about it is "the one you throw away", and worse, effectively everyone uses it as if they're building the one to throw away.
What's wrong with typescript? I was thinking of getting into it.
What language are you coming from? If I can do anything to stop you please tell me what that is.
TypeScript the language is fine. Almost great, even.
JavaScript the ecosystem is mostly a flaming garbage dump of worms.
You can take measures to lower the pain of being in a toxically incompetent package space devolving faster than you can type commands.
oh I don't plan to npm anything other than something like esbuild and solidjs. I don't do churn.
The one thing that would keep me from making the jump is CC’s auto mode.