• 0 Posts
  • 40 Comments
Joined 9 months ago
cake
Cake day: January 15th, 2026

help-circle

  • Is it an understanding failure, an unexpected interaction, or just an existing issue now exposed? A 23x performance increase could very well expose an existing race condition that systems weren’t fast enough to run into.

    People make mistakes. Software bugs existing at all is proof of this. This is certainly not the first time a change Torvalds approved has an issue, and it won’t be the last.

    There’s a reason code is reviewed, and there’s a reason people still go through after it is approved and verify. The process is working exactly as designed, the way it has for decades before AI coding.

    Expecting absolute perfection is ridiculous, the anti-AI circlejerk acting like only AI fucks up just makes them look ridiculous. Any developer could have developed this fix, and there would be no article. Nothing in this issue is specific to AI usage and treating it like it is somehow special just undermines arguments against AI slop and vibe coding in general.


  • That requires the person to know what they’re doing, and using the AI as the tool it is. That’s a proper use of generative AI in coding, to speed up a human-driven process with oversight.

    That’s not what AI slop is, AI slop is what vibe coders do. They don’t know how any of the shit actually works, they just tell the AI to do something, and modify prompting until it gives them something that works. They can’t fix the issues because they don’t know what was done in the first place.

    The problem is that both use types look identical to anyone not directly involved in the project. Things like Claude don’t tell you whether it was used by a vibe coder or a responsible developer, it looks exactly the same.


  • This certainly seems like Steam already had a bug open for startup performance, but it was always a lower priority than other things (because it wasn’t a breaking issue, and startup was still generally fine) so it was just never addressed. It may even have had a partial fix that hadn’t been shipped yet, waiting for another pass at it.

    Once Epic tried to use that as an attack, they just fixed it as the low hanging fruit it was.