top 69 comments

sorted by: hot top controversial new old
[–] 92 points 3 weeks ago* (12 children)

This whole situation reminds me of people's distrust for Big Pharma. Forgetting the actual problem and just assuming everything it produces is evil and will kill you. The problem with big pharma isn't that modern medicine doesn't work, it's that pharmaceutical companies charge so much for it that poor people are condemned to die preventable deaths in the name of profit.

The problem with AI isn't that it can't produce good code, it's that it's capable of producing a shitload of bad code at volumes no human can possibly review. It doesn't surprise me at all that the guy who made Linux can wrangle an AI to produce exceptionally good outcomes. The problem is that there's a million Joe Normals who are gonna try to replicate it with no idea how to audit the output.

  • source
  • hideshow 12 child comments
  • [–] 27 points 3 weeks ago

    Fair enough!

    I've been vocally against Linus AI advocacy, but I do understand all the points you make here.

    I don't like that a lot of stupid people will take Torvalds use and embrace of AI as gospel that AI is some be all end all.

    I also LOATH that he is indirectly benefitting fascist corporations that committed the largest theft in human history.

    But the code is good 🤷‍♂️

    To say I am conflicted, is an understatement.

  • source
  • parent
  • [–] 14 points 3 weeks ago

    Plus all the employees who've been forced to produce and sift through that garbage code, because their bosses bought into the hype and don't see the software for what it actually is.

  • source
  • parent
  • [–] 10 points 3 weeks ago (2 children)

    Isn't the AI problem the vast amount of resources needed to produce code?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 3 weeks ago

    Compare the resources used to the alternatives.

    Unfortunately, we will never enjoy the fruits of prosperity, because our system is designed to squeeze first, ask questions later.

    Instead of being reduced, human misery will be redirected, and little will change.

  • source
  • parent
  • [–] 3 points 3 weeks ago

    Text doesn't seem to be much of a resource hog, at least not compared to static images and video. For example, ChatGPT seems like it will go all day running text errands, though I've never dived too deep or for long. Want free pics? A handful a day, for now. Video? Only the most primitive options are free.

  • source
  • parent
  • [–] 3 points 3 weeks ago (2 children)

    Yet even for those Joe Normals, I kinda like the democratising effect that they're now able to produce software, or modify existing software for their own use. Just don't fool yourself into thinking it's enterprise grade. Understand your limitations. And don't spam open source projects with slop PRs because you think the AI makes you a software wizard.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 87 points 3 weeks ago (21 children)

    What gets me is that this is roughly the best-case scenario for "capable hands" — Linus knows this codebase better than anyone alive — and a race condition plus a 9% read regression still slipped through on the first attempt. Reviews and testing caught it, which is the system working, but it moves the bottleneck from writing code to reviewing it. And review doesn't scale the way generation does; skimming a patch is quick, but actually proving an LLM-assisted one is correct takes real effort. I say that as someone who uses AI tooling daily — reading code you didn't write is genuinely more tiring than writing it, and that tax compounds the more you lean on generation. The maintainer-burnout angle might end up being the real story here, more than the AI one.

  • source
  • hideshow 21 child comments
  • [–] 25 points 3 weeks ago (4 children)

    reading code you didn't write is genuinely more tiring than writing it

    What I keep saying. Good take except that you don't use "AI" tooling, you use copyright evasion slop tooling.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 3 weeks ago (3 children)

    I thought code couldn't be copywritten? It's instructions, isn't it?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 3 weeks ago

    I think it's still murky as far as AI generated code goes. (IIRC You can't, but not sure enough to say so authoritatively)

    But code historically has been very copyright-able. Oracle's business model was mostly buying companies and then suing people for infringing on their newly-acquired IP.

  • source
  • parent
  • [–] 12 points 3 weeks ago (5 children)

    Linus knows this codebase better than anyone alive

    Does he? Is it even possible to know the entirety of the Linux kernel within one head?

  • source
  • parent
  • hideshow 5 child comments
  • [–] 32 points 3 weeks ago (3 children)

    Does one need to know the entirety in their head to know it better than anyone else? If not Linus, who?

  • source
  • parent
  • hideshow 3 child comments
  • [–] -4 points 3 weeks ago (9 children)

    Verifying LLM code isn't necessarily harder than verifying a human PR. I hope that this also boosts automated test tooling so that it also gets easier to test these PRs, since the focus will shift to review rather than writing.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 18 points 3 weeks ago* (8 children)

    Verifying 10 pounds of incoherent architectural choices and over engineered submodules is certainly harder than reviewing tee bits of coherent human work.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 2 points 3 weeks ago (5 children)

    Sure, that's why I said "not necessarily". LLMs can be misused and made to do dumb shit too. But I have seen plenty of bullshit come from human developers too.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 3 points 3 weeks ago* (4 children)

    LLMs make dumb shit by default. Even Linus had a race condition caught in review when he used AI to bulldoze his way through a feature.

    Agentic loops have major flaws which humans don’t, a tradeoff you seem to keep ignoring while you suggest that developers and agents are comparable in their output quality. The only comparison is, at surface value, they both produce code. Deeper than that, there are plenty of tradeoffs.

    Yes tradeoffs in code quality, project quality, maintainability, technical debt, … you need to be a good programmer to get a good project out of an agent — and even that isn’t enough at times.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 3 weeks ago (3 children)

    At the architectural level, there's definitely a difference yes. But at the smaller scoped implementation level the latest models are pretty good compared to humans. Not perfect by any means, sure, but it's not all drivel anymore. It was 2 years ago, but today's definitely different.

    Race conditions are generally harder to catch, even for human devs. And you're saying it as if Linus wouldn't have introduced it had he coded everything by hand, which I don't think is remotely guaranteed (like he never makes mistakes). And the review system clearly works just fine still.

    Good developers can accelerate their work with agents, and you're right that you can generate tons of LLM-powered slop with it too. But that's why dismissing anything an agent wrote immediately is also wrong. The review determines if it's good enough, whether a human or an agent wrote it.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 3 weeks ago* (last edited 2 weeks ago) (2 children)

    I’m not really discussing smaller scoped patches, though. An LLM can change a single line in a file, sure, but the prerequisite there is that the file adequately contains the necessary context to do so. With small patches, you’re advantaged in that way.

    Larger patches suffer from a distinct kind of problem where the LLM can heavily over optimize submodules within the code, without proper consideration for the larger premise. This is a problem I’ve seen referred to as “decoherence.” In large projects, it can sort of take over the codebase after enough LLM engagement.

    Decoherence makes your codebase unmaintainable. The cost of every change increases logarithmically and the situation gets worse. The heavily optimized submodules are often incompatible semantically, so the agent also optimizes channels between them. This is an explosion in unwarranted complexity. This isn’t a human problem.

    Good developers can accelerate their work with agents. However, back to the topic on hand, reviewing agentic code changes is necessarily harder — because it’s prone to more issues that run far deeper. You have to review the code almost adversarially, with more cognitive load being used to unravel the gargantuan mess of barely sensible changes when viewed from a birds eye.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 weeks ago (1 child)

    You can also have multiple models review the result, seek consensus, and then review the results of that report. I find that's the best way to find legitimate issues, prior manual review. Huge time saver because the multitude of models can converge while you make yourself a cup of coffee, and you can find things that need to be fixed before you ask someone to spend their precious time in reviewing a pull request.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 2 weeks ago

    You don’t throw more oil on oil fires.

    Dont get me wrong, you can’t use AI to speed things up. But if you’re facing the problems I’m describing, then you need a targeted and explicit recovery effort — not just more bots.

    Remember part of the problem is the increased cost of every subsequent change.

    Humans will have this little voice in the back of their head, always screaming at them about how the architecture of an app should be adjusted to better account for a feature. We’re constantly reorganizing our apps, or backlogging features because we know that it should come with a reorganization.

    By contrast, an agent just does as it’s told. When you start using agents in a manner that outpaces your capacity to review and understand the breadth of its work, you’re necessarily ignorant of what changes should and shouldn’t necessarily be occurring. It creates the conditions for the problem which I’m referring to. Also, AI is really good at moving fast — so it created the preconditions of the conditions for the problem which I am referring to. It’s turtles all the way down.

  • source
  • parent
  • [–] 2 points 3 weeks ago (1 child)

    And verifying 10 pounds of incoherent architectural choices and over engineered submodules of human work is certainly harder than reviewing tee bits of coherent agent work.

    You are? I can also make false dichotomy fallacies!

  • source
  • parent
  • hideshow 1 child comment
  • [–] 12 points 3 weeks ago* (last edited 3 weeks ago)

    The difference is that AI is prone to this issue, even a single agentic process. Humans only really run into this issue with large, disorganized teams.

    Humans burn out.

    https://maevyn.codes/decoherence

    edit: hold up. Presenting as though what I said works in reverse,

    verifying 10 pounds of incoherent architectural choices and over engineered submodules of human work is certainly harder than reviewing tee bits of coherent agent work.

    as though agentic and human contribution is equatable… wouldn’t that be false equivalency? Tisk tisk…

    Human work is not swappable with agentic work without tradeoffs, which is kind of why I was making a point at all.

  • source
  • parent
  • [–] 75 points 3 weeks ago (32 children)

    Assuming these updates are fully tested before they're deployed, by a human, it shouldn't be that impactful negatively that AI is being used. The problem comes when updates are moved into production without human oversight.

    But it gives me the heebie jeebies, since AI is known to make and fuck shit up, and I'm stuck using MS Teams every day in my job so I see all the weird shit that vibe coding produces. I don't relish the thought of weird, stupid shit happening to my Linux installation.

  • source
  • hideshow 32 child comments
  • [–] 44 points 3 weeks ago* (last edited 3 weeks ago) (1 child)

    Plus studies on skill decay when using AI. Also the linux maintainer onboarding pipeline—which was already critically endangered—is now no longer building understanding through writing code, just monitoring it's generation.

    I personally think you need to write a language by hand without AI doing it for you to learn in detail. It's like trying to learn how to do math or how to write mandarin by just supervising an AI doing it... you need to do it yourself. Supervising is fine if you're already fluent in mandarin and have been writing it for years and years. If you're just learning it's less than useless. If anything its directly harmful to learning.

    Same with speaking a language yourself without crutching your native language as the best method to learn to speak it (immersion)

    Edit: The long term externalities of AI—like pretty much everything nowadays—is going to be made worse by short term thinking. Quarterly profits and yearly results take precedence over long term skill development. Even OSS like linux will eat its seed corn out of expediency because of a lack of maintainers and new candidates being onboarded into the ivory tower mailing lists...

  • source
  • parent
  • hideshow 1 child comment
  • [–] 32 points 3 weeks ago (21 children)

    Human review of AI is sufficient in theory, but in practice it's never as thorough as the understanding you get writing it yourself. It's hard to avoid AI, but it is a constant invitation to laziness.

  • source
  • parent
  • hideshow 21 child comments
  • [–] 19 points 3 weeks ago (19 children)

    Unlike reviewing a human who writes code there is zero chance of AI learning from the past and making fewer mistakes in the future. At a least a human has a chance of becoming better at coding from review feedback.

  • source
  • parent
  • hideshow 19 child comments
  • [+] -16 points 3 weeks ago (17 children)

    No? Are you not aware of the concept of "memories"? AI do indeed take feedback into account, if they're designed to.

  • source
  • parent
  • hideshow 17 child comments
  • [–] 18 points 3 weeks ago (14 children)

    AI does not have memories.

    It has a comparatively small context window that makes things worse the more it fills up.

  • source
  • parent
  • hideshow 14 child comments
  • [+] -12 points 3 weeks ago (11 children)

    You are mistaken. Some AI models do indeed have memories.

  • source
  • parent
  • hideshow 11 child comments
  • [–] 10 points 3 weeks ago (10 children)

    They save some strings in a document to later read and "remember". Calling them memories is a reach.

  • source
  • parent
  • hideshow 10 child comments
  • [+] -6 points 3 weeks ago (9 children)

    My point stands that they can learn from feedback. Your memories are only information in a virtual document, too. Just as susceptible to corruption, or misinterpretation.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 4 points 3 weeks ago (6 children)

    Does an Alzheimer's patient learn things just because they read the same note every morning explaining the reality to them?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 0 points 3 weeks ago (5 children)

    No, their file system is corrupt. No reliable read or write access.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 3 weeks ago (4 children)

    The AI is no different from the girl in "50 First Dates (2004)". It has to go back and read the post-it notes every time you start a new session. It does not retain memory without writing shit down to read later.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 3 weeks ago (3 children)

    You're not wrong. It's an inferior equivalent, but would you not say she learns with each note she makes, hampered though she is?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 3 weeks ago (2 children)

    Yes I would say that she temporarily learns something while reading the notes. And she stores it in short-term memory.

    The difference with AI though is that it has to re-read the same note again and again after each question you ask it. It does not keep things in "memory" from your previous conversations. It reads it again before answering you.

    That is why context length matters and is important in LLMs. There's a huge difference between talking to an AI with 10k in context length and 1mil in context length. You can try it yourself using Llama.cpp and running LLMs locally.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 weeks ago* (last edited 2 weeks ago) (1 child)

    Our short term memory is our context window. Some people have larger capacity for information, others very little. Same thing, different terminology.

    I use Ollama daily. The context limit of 10k is indeed very limiting and noticeable compared to the extended lengths of cloud models. I've had to recruit a model specifically trained on condensing salient information to perform context compression frequently. I also use the limited local context to establish effective strategies for maximizing token efficiency in the agent.md.

    It's no different from how many tasks a person can simultaneously perform, or disparate words they can hold concurrently. Eventually thoughts are forgotten. What exactly is determined by the structure itself - the context-pruning strategy inherent. We don't know what our own are, but I believe we have an equivalent.

    All I'm saying, in the end, is that anything that can occur in a physical entity can be emulated in a digital entity. Are we capable of doing that flawlessly yet? No, but it is looking inevitable to me. Neural networks are ubiquitous, and our ability to simulate them will only improve.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 2 weeks ago

    Sure, but I still think calling it "memories" is a reach and a bit disingenuous. It's not remembering anything. It's re-reading it will the every run, making it appears as if it has remembered. Calling it "reminders" or something else I think would me more appropriate.

    The "memories" terminology comes from the big AI companies and they are doing everything in their power to make AI seem smarter than it actually is. A lot of reporters in media has a hard time understanding this as well and will report on AI as having it's "own thoughts" and "making own decisions".

    ChatGPT breaches confinement because their engineers are stupid. Not because of some self determination to fuck with us or our infrastructure. OpenAI are responsible and let it happen. Same with Anthropic.

    In the end an AI is a dumb computer program that only know and does what we tell it to do.

  • source
  • parent
  • [–] 9 points 3 weeks ago (1 child)

    The auto-generated memories I've seen it create are pretty inane: "always name variables container_ when in MySpecificClass". Not really learning engineering principles.

    Similar, I've found AGENT.md files might nudge it in the right direction, but as always it's a fuzzy matcher, not a learning engineer.

  • source
  • parent
  • hideshow 1 child comment
  • [+] -8 points 3 weeks ago

    It's best to generate memories manually, but I've had good fortune with auto-generated so far. At least using Co-pilot.

    I have found it best to have another AI generate the agent.md - having a layer of interpretation can really clarify the information imparted.

  • source
  • parent
  • [–] 22 points 3 weeks ago (5 children)

    One thing I'm noticing about AI code is it's very, very task oriented. Like it will produce code, that works for the one objective, but absolutely will not account for other interactions with other parts of the system. It's really bad at juggling multiple priorities so for every solution it creates, it causes another 2 problems with other parts of the stack. Human coders would design a solution that takes those interactions into account from the ground up. With an AI solution, you kind of have to rebuild those interactions as an afterthought, which is where a lot of failures occur. Since interaction of multiple subsystems is kind of the whole point of a kernel... I have concerns.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 3 points 3 weeks ago (4 children)

    Human coders would design a solution that takes those interactions into account from the ground up.

    Lol, this only happens in Utopia

  • source
  • parent
  • hideshow 4 child comments
  • [–] 13 points 3 weeks ago (3 children)

    Utopic might be a bit of a stretch, but I should probably qualify that as good human coders.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 7 points 3 weeks ago* (1 child)

    it shouldn't be that impactful negatively that AI is being used

    Doesn't it invalidate the GPL? Open source licenses depend on copyright, and LLM-generated code isn't copyrightable.

    (Also, it can't be proven not to contain plagiarised proprietary code, in fact it's quite likely that it does; between this, the testing / review burden, and the mental decay of developers that use LLMs instead of coding, this pretty much kills open source projects, in several different ways to make sure they stay dead...)

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 3 weeks ago

    It's not that they're not copyrightable. That court case is misunderstood. The vibe coder tried to give the AI the copyright and the judge ruled that was stupid because AI can't own shit.

    Also copyright doesn't mean much anymore because companies are rewriting open source software as copyrightable vibe coded bullshit the same way people are "open sourcing" Adobe using vibe coded crap.

    It's garbage "progress" all the way down.

  • source
  • parent
  • [–] 18 points 3 weeks ago*

    It’s funny how the “AI-assisted” in the headline turns into an “LLM-assisted” in the article.

    The graphic with the magic “AI” hand is even funnier.

    Clown “AI” journalism.

  • source
  • load more comments
    view more: next ›
    22 comments in c/linux@programming.dev view that post