Comment by ImaCake

4 days ago

They REALLY don't like AI, to the point of "wish I didn't need to rely on GCC and GRUB because they have AI in them" levels of hate AI. See this further down the linked page:

>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.

> U-Boot upstream itself is staunchly anti-AI, at least at the time of this release, and much discussion of the above was had on their mailing list.

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.

I have learned to treat statements like that as a general red flag.

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.

  • It's possible this type of "radical" behavior is why this project exists in the first place. I'm willing to bet if the Libreboot maintainer(s) were not "radical" they'd just be using a Mac and be content with a closed source bootloader.

    Not to say this "radical" behavior is helpful, and I understand why people don't like it.

    • The timeless debate of separating art from the artist.

      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.

      1 reply →

  • AI in its current form is a commercial product created from stolen labor.

    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.)

  • When your project is literally writing a BIOS/ UEFI alternative that exists for the purpose of making base runtime systems open and verifiable and to improve the user’s ability to trust in their system, an opposition to unverified machine generated code seems not only justifiable but sensible. If Leah were not taking steps to mitigate generated code in the project, the project would no longer meet my needs as a Libreboot user.

  • > 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.

    Not using LLMs is a practical choice. The tech doesn't work, and if you let it run amok in your software, your software becomes crap. I try to avoid projects that use LLMs for development as much as I can, because those projects have a much higher likelihood of being a buggy mess.

  • I find it hard to square treating that like such a red flag while supporting free open source software more generally. The entire ecosystem is rife with ethics/morals driving the initiative. There is a lot of flag planting and red line drawing.

    People say AI or not, if the thing is good then it should be used. But if a group actively rejects it (which is valid even if I’m not that militant myself) it compromises the project suddenly?

  • Personally I treat whinging about other people's ideals as a red flag.

    It's libreboot. The entire point of its creation was to take coreboot and rip out the non-libre blobs. Its author is trans (IIRC), which also carries its own very pointed perspective on the world.

    Some of it goes too far in my own opinion - I have no problem trusting AMD's final microcode for the Opteron 63xx any differently than the baked-in mask for the 62xx. But regardless, I respect someone who is pushing the whole envelope as they see it. At the very least their effort creates a lot of things I do care about!

    • Rereading this I realize I might be in the running for the RMS award for technically correct social obtuseness so let me just say that my intent was not to denigrate trans at all, just saying that being trans is itself intrinsically political (as in you're going to be continually clashing with many people's default assumptions, even before the manufactured "culture war" throws gas on the fire). And then furthermore being openly trans is going to impart those politics to the project. Which is most certainly her right, as it is her project! In fact I would say that trying to push a standard of you can contribute your code but stfu about your other ideals is basically cruel.

  • Well, yes, this is a project to create a fully libre, GPL'd boot chain free of binary blobs. The few users I know stick with aging ThinkPads. I'm not sure what you expected.

  • Yeah its quite the contrast to the recent QGIS core "no AI" policy that very pointedly had no emotive language at all.

  • Likewise, it if claims something is “vibe coded” when it clearly is not (such as U-Boot).

    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.

    • And what happens when the AI bubble pops and the various publishers and IP rights holders come around with their hands out claiming 86Box stole their code ala' SCO?

      AI code is legally nebulous and relying on it for a serious project has major risks. Linux has already fended off SCO and has deep pockets to boot. Not all open source projects do.

      More projects should be thinking less about the 'moral' issues (yes, they exist) and more about the nuts and bolts province and liability issues of using unverifiable code.

      Yes, Linux uses it -because they're big and professional and have allies like IBM and Microsoft (ironies of ironies) on their side.

      YOU do not.

      2 replies →

  • Yes, anti fascism is a radical position these days.

    Already in 2022, before the rise of these LLMs, there was a book "Resisting AI: An Anti-fascist Approach to Artificial Intelligence" by Dan McQuillan.

    And then:

    > The rapid development of digital technologies, including applications of artificial intelligence (AI), is having a significant impact on the social, economic, and political life. From the way individuals communicate and form relationships to the methods by which political discourse and economic transactions occur, digital technologies increasingly mediate our lives and societies. But while presented as milestones in innovation and progress, these technological transformations have also raised concerns about democracy (Nemitz 2018; Kreps and Kriner 2023; Jungherr 2023; Coeckelbergh 2024) and seem to introduce and support mechanisms of control, forms of organization, and ideological patterns that bear striking resemblances to historical fascist phenomena.

    https://link.springer.com/article/10.1007/s00146-026-02862-9

    Further,

    > being plausible but slightly wrong and un-auditable-at scale-is the killer feature of LLMs, not a bug that will ever be meaningfully addressed, and this combination of properties makes it an essentially fascist technology. By “fascist” in this context, I mean that it is well suited to centralizing authority, eliminating checks on that authority and advancing an anti-science agenda.

    https://blog.bgcarlisle.com/2025/05/16/a-plausible-scalable-...

    Marc Andreessen have called one of the two authors of the very Fascist Manifesto his patron saint. Search for Marinetti on https://a16z.com/the-techno-optimist-manifesto/

    A very influential blogger, Curtis Yarvin who have started Dark Enlightenment, the philosophy behind it all regularly posts straight nazi shit. He also has influenced JD Vance and Peter Thiel who have been instrumental in the creation of OpenAI. https://www.wired.com/story/book-excerpt-the-optimist-open-a... More on Dark Enlightenment https://www.cccb.org/en/w/articles/nick-land-or-the-origins-... and https://qz.com/1007144/the-neo-fascist-philosophy-that-under... "a few consistent themes, circling around technology, warfare, feudalism, corporate power, and racism".

    I know this won't be popular with this crowd but most of you have become supporters of the rising fascism in the United States by not resisting these LLMs.

    • US Vice Presidents have a history of inventing important new computer technologies

    • > Yes, anti fascism is a radical position these days.

      Given that these groups are basically composed of communists, if not tankies, that's not surprising. Specially when some of those served as sabotours for the USSR (notorious for its respect for human dignity).

      > https://blog.bgcarlisle.com/2025/05/16/a-plausible-scalable-...

      This is an incredible piece of anti-intellectualism. Its arguments aren't compelling either: AI might flood with innacurate studies that are difficult to check. Rather than improving said check as to reduce the reliance on trust and improve science as a whole; like the good reactionary the author is, they proppose to ban this particular technology. AI also centralizes authority... because? There is also an irony in them complaining about this theoretical centralization while also trying to preserve the inherent trust-based system in academia, so I suspect they aren't actually committed to proper intellectualism. There is more to complain about this post, but, then, it would hijack this whole comment.

      > Marc Andreessen have called one of the two authors of the very Fascist Manifesto his patron saint. Search for Marinetti on [...]

      Is it surprising that the guy who founded Futurism, a rather radical and aggressive celebration of innovation and progress, would be mentioned in a movement about technological progress?

      > A very influential blogger, Curtis Yarvin who have started Dark Enlightenment, the philosophy behind it all regularly posts straight nazi shit. He also has influenced JD Vance and Peter Thiel who have been instrumental in the creation of OpenAI.

      JD Vance hasn't been instrumental to OpenAI's creation, and Peter Thiel is just one of its original investors. Not to mention, NRx is a mess of movement composed of contradictory ideas.

      I have noticed you have been using "these LLMs". While I do agree that distancing from OpenAI's models is good (even if it's just on the basis of decentralization), the anti-AI movement either wants to monopolize AI via regulation or ban it outright.

  • I wouldn't trust their products simply because AI as a tool works and their refusal to use it means their software will be worse off for it.

    • This is just as bad as blanket hating/rejecting AI without ever trying to use or understand it. I don’t care what tools a craftsman uses so long as the job is done correctly/well. If you can somehow prove that AI is necessary for this that’d be impressive.

      2 replies →

> de-slopping them and possibly even forking

Or, hear me out, they could instead just improve and contribute the code they think is suboptimal

  • I put "de-slopping" in the same bucket as "rolling your own crypto" and "let's rewrite done software in Rust just because".

    • Seems more like clean room RE to me, or general free software stuff. You can't contribute proprietary code to free software, if someone doesn't agree to a license change you have to remove/rewrite their contributions, if you've seen the Windows source code you aren't allowed to contribute to ReactOS (IIRC), etc. LLMs are black boxes with dubious training data and aren't really "you" writing the code directly, so whether you can then license that is questionable. This is especially important for a project like LibreBoot that is trying to liberate machines. The only "easy" solution I see is to abolish copyright, which would be fine. As it is a lot of software is being tainted and the whole world of free software is in danger. It's a shame people gloss over this because they think LLMs are cool or help productivity or whatever. Everything's been irradiated now. Now if someone wants to guarantee a given project had no AI contributions they have to fork a years-old version and likely lose a lot of good non-LLM code in the process. What a waste of time and resources that is. Setting us way back. This needed to be taken way more seriously on day 0.

  • That's in the previous half of the sentence you removed:

    > ...it is my intention that I and others will audit these projects in the future, de-slopping them...

    • That's not what it implies to me. And let's not pretend that a person with this approach and this manifesto is going to publish their patches to deslop slopped upstream projects.

  • contributing to projects that have slop in them has legal liability. you'd have to essentially hardfork to remove the slop from git history and such.

    for my part, when i do work on this, what i will do is this: re-use existing nuke.list mechanism in lbmk (used already to delete dubious files, e.g. code files with unclear licensing in u-boot) to delete the slopped files. then provide cleaned versions of the same files, with necessary patching re-written as necessary, and files that use it patched to include e.g. foo.deslop.c instead of foo.c - then git history is removed inside tarballs. filter out the changelogs for projects accordingly.

    this is the most reasonable way to do it on projects with very little slop. with projects that become almost entirely slop, a hard fork becomes necessary.

  • > think for yourself. AI will only ruin your mind and deskill you. here are some articles:

    > think AI makes you super hacker? think again: https://arxiv.org/abs/2507.09089 ["Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity"]

    > https://blog.codeberg.org/protecting-our-floss-commons-from-...

    > consider that the infrastructure for AI is economically unsustainable; when the bubble bursts, and it will, we will suddenly be left with millions of people thoroughly deskilled who will be useless. lots of reeducation needed, and lots of people will just be left behind.

    > consider that it is controlled by only a minority of very wealthy individuals; with it, they have unprecedented control over human thought through manipulation of information, and control over what information is presented through filtering (what they call training).

    > AI is a threat to the health and democracy of our entire world.

    > libreboot will not facilitate its use. AI is the most dangerous technology ever invented by human beings.

    ...

    They have plenty of reasons not to.

    • > Early-2025 AI

      This one especially really just shows they are cherry picking things which support a particular position regardless of the relevance, the difference between Early-2025 AI and Late-2026 AI is absolutely massive. Early 2026 it was reported by Greg Kroah-Hartman that AI bug reports rapidly went from obviously wrong or low quality to being real reports.[0] The kernel now has AI tooling heavily integrated into patch review workflows as well with quite good results.[1]

      > They have plenty of reasons not to.

      Not really any good reasons however.

      [0] https://www.theregister.com/software/2026/03/26/linux-kernel...

      [1] https://github.com/sashiko-dev/sashiko

      5 replies →

    • > when the bubble bursts, and it will, we will suddenly be left with millions of people thoroughly deskilled who will be useless. lots of reeducation needed, and lots of people will just be left behind.

      what do you mean by this, that costs will become too high and people won't afford it? hardware won't go up in smoke "when the bubble bursts"

      1 reply →

Uboot on x86 is like a snowplow on a hatchback. Sure, it can work, but why?

Grub is more extensively used and has a lot of features. Or boot Linux on UEFI using a UKI executable without any bootloader.

How terrible. I'm sitting on multiple AI reverse engineered firmwares that I'm not sure what to do with. I suppose they'll never make it to upstream now. My only option is to ask AI to integrate this stuff.

  • This conflict has come up a lot in open source lately and the answer has been to just create your own repo and space where you can dump unlimited ai output without needing anyone’s permission. If users find it useful they can use it, and there’s no conflict with maintainers who don’t want it.

    Time will tell if these new AI allowed projects like artcraft will prove more popular than fully human curated ones.

    • The whole point of open source is to get this stuff upstream so that a rich software commons is created.

      I'm not sure I want to participate in this space anymore if everyone is just going to have their own isolated forks. I might as well keep my own private version of everything and never deal with maintainers ever again.

      3 replies →