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.
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.
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.
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.
Yup - IMO it’s just the wrong tool for the job.
> 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.