shork @noiob@awoo.space

I have put up with TypeScript for multiple years at this point. in that time, I have argued with TS devs about how the language is fundamentally unsound and that they don't understand type theory, when they decided that my soundness issues should be "won't fix."

recently, a particular pain point of TS was brought up at work, where the official definition of JSON.stringify is annotated to always return string, which is wrong.

I decided, yknow what, I'm feeling particularly motivated by rage, so, I'll try and put up with M$'s bullshit PR workflow. I'll sign their BS CLA and agree to let them yoink away the code at any time so I can fix a ridiculous bug that was filed years ago that no one at microsoft has bothered to fix. at work I joked that old bugs don't make for good press, and thus the solution is to never fix old bugs, but it honestly might as well be that way with TS.

their contributor guide is full of the usual "oh don't just fix a typo, it increases the maintenance burden of our poor engineers" despite the fact that TypeScript is managed by a fucking trillion dollar company with an iron grip on the entire JavaScript ecosystem. you absolutely can afford to not patronise people wishing to help out with the project, but you just don't want to.

anyway, I went through their terrible, poorly explained flow to upgrade all of their compiler tests that for some reason explicitly encode the line numbers of things inside these source files that should change often. I had to go through multiple different docs to figure this out and try stuff out because they do not make it clear. they don't pay anyone to write docs, clearly. however, it's worth pointing out that they recommend using WinMerge for a diff tool! because it has Win in the name! get it, we're winning? Windows? no?

oh, and they also recommend VS Code, because hey, we made it!!!!!!!

like, I don't expect people to respond every single day (that'd be absurd) and I'm sure someone relatively kind will get back to me by the end of the week and help get this out of the door. but from the stuff I've seen, multiple people over multiple years have tried to fix this exact bug, and then due to it not being attended to quickly on a repository which merges multiple changes per day, it quickly got out of date, and then the person who started it didn't have the resources to actually fix the errors that were literally created by them not responding to it quickly

like, hey, when people complain about companies being shitty to open source, this is exactly what they're talking about, Microsoft.