Replies (2)

• @self@awful.systems 2026-10-15 11:30

  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!

  Open ##5045971

• @BritishPork@sh.itjust.works 2026-10-15 11:50

  I’d consider both, and he seems much better over the past decade or so.

  Open ##5046182