anyway since we’re here (well, you’re not but fuck you) here’s your pissboy programming god’s latest: https://mas.to/@zzt/117452262149452021 enjoy! go fuck yourself!
you kids are so fucking desperate for your programming god to not suck
update: the patch set from Linus Torvalds, Boy Genius, went into review and the reviewers immediately found a race condition: https://woof.tech/@techokami/117446164348546588
wow! it's really easy to write fast kernel code when it's wrong
and now he's apparently just dumping it on someone else because he's "going on vacation", a move that post-LLM commercial developers on most teams will be extremely familiar with
god, imagine the system we'd have if working on this shit didn't fucking suck due to guys like torvalds
I mean, given that I'm typing this from an X window managed by emacs emulating vim...
both vim and emacs are really good editors with an ecosystem of modern features (and a bunch of stuff that goes beyond what IDEs usually provide too). unlike an LLM, an editor is a tool that rewards learning. the problem is, guys like Torvalds are so unwilling to learn a new way of working that they turned the horrible way of working they started with into a fetish, and they made that fetish everyone else's problem. there's a lot of horrible development practices in the kernel that stem from conservatism and an unwillingness to learn.
and as it turns out, LLMs are perfect in so many ways if you're an overwhelmed conservative trying to hold onto power without ever having to learn a damn thing again.
weird how all the assholes who insisted on making programming worse for themselves and others are now fully addicted to LLMs
oh and who can forget:
at that same fucking summit he talked about how LLMs were irreplaceable tools for modifying the callers of a function whose signature you changed, a thing that IDEs have been able to do much, much more reliably and faster than LLMs since... the 80s I think? possibly the 70s? and they don't drink several bottles of water doing it. they don't even spike your CPU. it's such a basic thing for an IDE or an editor plugin to do. ctags is a command line tool for this that came with fucking BSD 2.0.
but torvalds famously used to only use a version of microemacs from 1987 to work on the kernel, an ultra cool choice that doesn't even support syntax highlighting and later forked to become... nano of all god damn things
so now he's ultra-impressed by the basic shit you can do, because like a lot of programming dickheads he never learned any of his tools properly and made it everyone else's problem
and now like an MBA who thinks he can slop out a billion dollar app, his fried brain thinks it's so impressive when the LLM does the basic editing tasks he never learned to do himself but much slower and much worse than an editor. and like that same MBA when his project's burning to the ground, he's shouting that it's his underlings' faults for not learning the LLM properly, for not prompting it right. no he won't share his setup, because if he did it'd become very obvious he's out of his fucking depth.
godlike programmer my ass
but it's so much harder to glaze the guy if you pay any attention to anything he's done in the current decade:
- receiving a gigantic paycheck from the Linux Foundation, almost all of which comes from AI corporations and their affiliates
- failing to learn basic frontend Python for a side project and getting overly impressed with Google Antigravity (whatever the fuck that is) slopping it out for him
- changing the kernel's LLM policy based entirely on that experience to force engagement with a (reputedly horrible, but that goes without saying) LLM review bot and slop commits and responding to the pushback with "Linux isn't a social warrior project", a sentence that's fractally incorrect and also a callback to the old SJW right-wing conspiracy theory
- entirely slop-coding core kernel features, tests, and docs because Claude Code rewrote an old patch in a way that impressed him and that sole experience was all the excuse he needed to decide that LLMs are good at kernel code, in spite of all other projects to write less complex systems code with LLMs (Anthropic's slop browser, Anthropic's slop C compiler, bun, rsync, the open source firmware for the Xteink X4, MeshOS, that one disaster System 7 clone, probably more) ending in disaster
- deciding at a closed doors maintainer summit that LLM commits no longer need to be tagged as such, eliminating documentation stating that the tagging was done as a quality control measure and making it impossible to tell if the coming shitstorm of issues for the kernel are due to LLM code (but they absolutely are)
- declaring at the same summit that the kernel no longer wants inexperienced maintainers; that all maintainers are expected to either have the wealth to pay for Claude Code or to educate themselves (the latter learning path being by bashing their heads against LLM-generated PRs and the LLM CI nagbot that flags human code much more frequently than LLM code until they burn out, from long personal experience with slopified projects)
- declaring at that same cursed fucking summit that LLMs work great if you set them up right and using the old patch as "proof" (a common blame-shifting move in corporate teams using LLMs) then refusing to share his setup or the steps he took to clean up the old patch (also a common move in corporate teams using LLMs)
but if you paid any attention to any of these things, you might think he's an asshole accepting money and tokens (he doesn't pay for any of his own LLM usage) from some of the most corrupt corporations in the world in order to wrench control over Linux away from its own community
and that would be crazy!
I'm purging the worst of the conspiracy theorists (which I'm sure they'll love)
I considered posting a reminder that we do analysis here, not weirdo daydreaming, but fuck it anyone who doesn't know where the line is deserves a ban
that's great thanks
view more:
next ›