Besides considering frontier LLMs a serious threat to humanity, I find LLM-assisted programming simply...not fun! I tolerate only AI-assisted bug reports, as they are genuinely useful.
https://codeberg.org/libreboot/lbmk/src/branch/master/AGENTS...
>The fork in question, of U-Boot, is heavily AI vibe-coded and thus useless to Libreboot. This is not mere conjecture; in said aforementioned U-Boot mailing list thread, the author stated thus. We will not, in any way, encourage or facilitate use of AI. It has been made clear that several projects Libreboot uses also have some AI-assisted commits; GCC, GRUB, etc. This is not our fault, but it is my intention that I and others will audit these projects in the future, de-slopping them and possibly even forking them entirely for that very reason.
I saw this as well, which is funny because I've sent plenty of patches written using AI assistance to upstream U-Boot. It was my understanding that U-Boot was mostly following kernel conventions in general as many U-Boot drivers share code(in addition to the actual subsystem maintainers themselves) with their kernel equivalents.
Someone who acts like a radical on practical issues will almost certainly act like a radical in other areas as well - including areas that matter to me.
There are debates to be had on every technology, but foaming-at-the-mouth kind of talk is a sure sign of a maintainer (and by extension a project) I want nothing to do with.
I respect projects with a no AI policy, but if that policy starts with the words “fuck no”, I’m out of there.
Also
> https://codeberg.org/ethical-foss/open-slopware
Feels more like a software discovery list than an indictment. Thanks for the categorization.
You're not kidding, I feel like this is better than most of those awesome-X lists that were popular for a while.
>"think AI makes you super hacker? think again: https://arxiv.org/abs/2507.09089"
not that im particularly pro-ai, but it seems a bit silly to rely on a paper about early-2025 ai when people are using late-2026 ai, given how different they are.
The right way is something like, we've been getting spammed with a bunch of PR's from AI that we find difficult to review (because AI allows the average bob who isn't technically minded to make a PR). We have therefore decided not to allow AI submissions.
---
I think the people who have some moral / ideological issue and bring that into projects kind of feel like clowns to me. I agree with Linus that the point is to make something that people find useful, and obviously you want it to be maintainable.
Saying "it makes you dumber etc" is not related to the project, with all due respect it's non of your fucking business how I learn / retain skills.
I feel people have the right to bring any sort of issue into the projects they make. Nobody is forced to participate.
You can't expect to sufficiently protect your users privacy when not using AI for finding vulnerabilities.
Same thing with Asahi Linux with their highly anti-AI stance. I had a bit of hope when I saw someone was making an LLM assisted fork but it's not the same support.
While MacOS is likely becoming much more secure, Linux distros that reject AI would fall even further behind, if that's possible.
Edit: added critical
The Linux kernel extensively uses AI now; most lkml submissions have an Assisted-by: LLM tag.
Fork it and use Ai if you have a problem.
Coreboot still exists.
They're making a political choice. It's a free country, and more power to them.
It's not a choice that I necessarily agree with, but one that may - who knows - prove prescient 5 years down the road.
No one can predict the future, that's what politics are partly about and the reason why diversity of opinion of choice matters.
Do you have a crystal ball?
(Signed, the owner of several Chromebooks in need of better firmware)
The Linux kernel has always been focused on outcomes and outputs, which is the right focus. Here's Linus: https://x.com/LundukeJournal/status/2110524360377458786
Outputs: Code quality and long term maintenance matters. Outputs: Serving users with correctness, security and performance matters.
Focus on "purity of input" is a faith-based political filter, not engineering.
Someone should ask him if he's also planning on no longer reviewing patches to the kernel and just accepting them unconditionally, since AI is no different from a compiler after all, and nobody reviews compiler outputs.
It's their own business to disallow AI contributions. But instead of adding that to the Code Of Conduct they chose to knowingly misuse a file to target a group of people they don't like.
If I want to use AI on my copy of that repo, I have to delete that file and consider if the developer has added any more of what is (by intent) basically malware to the source code. Sure the file is just an unhinged rant, but now I have to wonder if they attempted to put some prompt injection in the repo.
I'm now working on the 2nd ChromeOS device in this PR right now: https://github.com/linuxboot/heads/pull/2225 And there is a 3rd port by someone else: https://github.com/linuxboot/heads/pull/2219
I'm surprised Libreboot was able to add all the ChromeOS devices at once, Just adding the 2 ports for Heads hasn't been easy, although I'm not an expert when it comes to Coreboot.
Anyway, I love seeing more support for Chromebooks, they are great devices. Funny enough my Acer Chromebook (Kano) is now more open and more secure than my Framework 13s.
It may be harder to port it if those features require neutered (rather than simply removed) blobs. Maybe that’s why the Libreboot port was easier? Not sure, I’m aware of the benefits that Heads provides but I don’t know much about the internals.
Either way, thanks for your work on this.
Nice. I think I loaded MrChromebox onto my Google Pixel some years ago. I should see if it can get Libreboot now.
How so?
It's a distribution. That is, they build and distribute firmware images. Coreboot just ships source.
Coreboot's docs lists the variety of distributions: https://doc.coreboot.org/distributions.html
Yes, and that take is bad, because AI is not a tool in the traditional sense. In the software world, tools are generally expected to be deterministic. Would Linus use a compiler that is known to have a random chance to output the wrong instructions? Or an editor that has a random chance to swap something you typed for something else?
> compiler outputs are tested by the compiler projects + the automated testing infra
And AI outputs are tested by the AI companies and the various testing suites that are run on the kernel. If they're really the same like Linus seems to believe, there's no reason to ever read AI generated patches before merging them.
You can look at what being achieved right now with AI, GoW3 (an absolute master piece BTW) on the PS4 Remaster can be played on Linux at 120FPS thanks to some decompilation/reverse engineering framework with AI.
I am generally also fed up of politics (whatever they are) forced into projects.
Also AI doesn't make you stupid. It is bullshit, he has cherry picked information to sooth his own biases.
Not to say this "radical" behavior is helpful, and I understand why people don't like it.
In another project (literally: "Untitled") of theirs they are explicit about motivation:
> This is to fight against the trend of crappy github-powered websites that plague the internet.
I think there are extremely legitimate reasons to be critical of that part at the very least, and I don't think it's a particularly "radical" stance within Free Software, which is fundamentally conscientious of such questions.
(I don't know whether the Libreboot authors have this particular point in mind.)
Agentic AI has allowed 86Box to make massive strides forward. This includes a substantial contribution to emulate the Intel Inboard 386 that was created by someone who describes himself as a non-programmer. The community is now bigger and stronger, although we’ve had some aches and pains with slop AI generated PRs.
The same goes for Gravity Linux which is booting in my M4 Macs with working GPU and most other peripherals. What used to take years now takes weeks, so we can do much more thorough testing and ultimately have a better end product.