“tsc does not follow semantic versioning, so even minor updates can introduce changes to type checking that may break existing code.” — @satanacchio.bsky.social
Zach Leatherman 1717 replies 1818 likes22 reposts22 quotes Original on Bluesky17 replies
the irony of a strongly typed superset of JavaScript that doesn’t follow semantic versioning is *wild* — we see that, right?
"one type checker to find them and in darkness bind them"
*wakes up in hospital*
“we’ve given you a blood transfusion in your left arm and we didn’t even need a blood donor because we used blood that we took out of your right arm”
A lot of typescript features tighten the type check. All of these errors would require major bump according to semver
they can use semver just 0.x forever 😅
It’s funny that every time this comes up there is a new host of people surprised. Yet the ecosystem just keeps inefficiently chugging along as if all of this is predetermined destiny we cannot change. All hail Microsoft, the owner of our entire developer platform and shaper of our destiny.
look, I’m genuinely okay pushing a rock up a hill as long as it’s my choice to do so
Or is it merely the illusion of choice?
it isn’t an illusion if I choose to ignore that possibility
“I built this house out of cards with my two bare hands and I love it” is actually very much in line with my beliefs that all we are doing is craft with a little bit of art dashed in.
Maybe if I didn’t have to work a job that forces me to think about how “productivity” can be optimized I would love the fact we have projects that take an “artisanal” approach to stability 🤣
rip ur mentions
NUCLEAR MUTE
its the only way to be sure
This may be what I'm trying to fix just now. Just moved to 5.7.3 and working stuff broke.
I don't like to write plain JS, but JESUS the TypeScript ecosystem is insane. I wish it was easier to write JSDoc to get some sort of type info, but TS just makes it easier to write