this post was submitted on 11 Jun 2026
89 points (97.8% liked)
Fuck AI
7325 readers
1530 users here now
"We did it, Patrick! We made a technological breakthrough!"
A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.
AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Actual comment proving it's bullshit: https://github.com/rhinstaller/anaconda/pull/7074#issuecomment-4556782893
But the PR is still merged. What does that mean. They just accepted it anyway? ๐ข
Edit: it was reverted, I hear ya ๐๐ค
Yeah, I was reading the comment before and anyone with a vague awareness of this stuff should have called bullshit immediately.
Preserving the argument seemed an innocuous enough change though, so I could see why it was accepted, but the explanation was bafflingly stupid.
But people who don't know eat it up. Sounded possible (until they claimed the system crashed and could not log the error, despite a log entry belt there that they ostensibly cite as the issue..).
I just don't understand the workflow with these people.
You know how people say "don't run a command you are given or find online unless you know exactly what it does"?
Why would anyone accept/merge a PR from an LLM unless they knew what the consequences were, or verified its claims. I just will never get this trust in LLMs, given I know even vaguely how they work.
That's probably a good stance to have. I just had an AI hallucinate the hell out of an answer and tell me 3 different times the wrong thing. I took a step back, started a new chat, and changed my question to be less specific and more general and the very first thing it spit back was bang on right.
This is just in regards to figuring some shit out in a video game, it's alarming to me how much trust people are putting into these LLMs and the AI tech. Just a huge bubble that's going to wreck our markets when it bursts. Eventually venture capitalists (ew) do want a return on investment - and that just is not going to happen.
I think the great AI bubble burst, whenever that happens in the next 1 to 3 years, will make the dot com crash and 2008 housing crash look like peanuts and that's gonna be real bad for lots of people.
But hey, the earth keeps on spinning, we're just along for the ride.*
*Unless you're a filthy rich member of the borgeousie, in which case, for the love of God have your tech buddies reign this shit in.
Well, in this case, the actual change is pointless, but also relatively harmless. If the user puts "split_lock_detect=" during install, then it just carries it forward into the installed environment.
It's frankly a bit weird that they assume a kernel argument during install would not carry over, except in select circumstances. I get it for parameters like "here's a kickstart file" or "here's the net configuration to boot with", which would be filtered out via a blacklist, but they have a whitelist and assume most parameters should be ignored.
But anyway, I can see someone looking at the code change, not recognizing why someone would want that argument, but shrug and say "sure, simple enough, it won't impact the vast majority of people and those that bother for whatever reason will just see it carried forward".
But clearly it wasn't something anyone wanted as it was later reverted, and not kept in because it was supposedly harmless.
I get what you're saying though. I'm just glad someone in those comments actually analyzed the situation instead of putting their trust in the charismatic LLM. Those people still exist!
Funny part is that if it just stated "sometimes the user needs this argument, and if they need this argument for install they will need it to boot", they might have shrugged and let it slide. In trying to overexplain, it betrayed that there was no actual understanding behind it.
That's what happens when you don't actually understand the change and just listen to whoever is posting it. The disingenuous thing about LLMs is that they present their hallucinations with full confidence in a charismatic way. No matter the source, that is how anyone can mislead other humans, we're just so extremely susceptible to it.
Judging by the leaders of the world throughout history โ yes we are indeed. And it's so sad.
Looks like it was reverted later?
Looks like it was reverted shortly after the comment you posted.
I didn't notice that. The fact that Redhat is merging random crap is scary.
Well, this case the actual little 'code change' is pointless, but harmless, so not so scary. The rationale is stupid because the purported root cause makes no sense against the behavior, but preserving a custom boot parameter added to install to also apply to the installed OS is pretty milquetoast.
Not really, it matches the Redhat software quality that we had a joy to experience for the last 10+ years (systemd, pulseaudio, Gnome, ...)
GNOME is getting bad but in my experience systemd is just drama (and fine) and pulseaudio is still just fine
What would you say is low quality in those projects you listed there?
Also didn't know Redhat developed those.
How long have you been around in the linux world? All of them were absolute dogshit when they came out and everyone complained (for Gnome, that means Gnome 3), but redhat kept pushing them anyway. For instance, when pulseaudio was new it caused crackles, noise, high cpu etc. everywhere, but they used their business connections to have vendors support pulseaudio exclusively, which meant you had to install it if you wanted to use Skype or for various games, even though ALSA was (and is) just fine. Nowadays it gets replaced by pipewire.
I guess I don't need to explain the systemd drama; it has gotten much better, but what still sucks is that it drops you into a rescue mode when it can't mount some filesystem that is not even necessary for boot (e.g. /mnt/data). And when you do not have a root password set up, but use
sudofor everything, you are screwed because systemd demands the root password nevertheless, meaning you gonna need to boot from a live usb or similar just to fix one line in fstab. That is the stupidest shit imaginable.How would business connections work? And it was only problematic on some systems, and only for a while
the audio situation before it was a total fucking disaster lol. The only real f up was no low latency really which pipewire now fixes apparently
And systemd consolidated and fixed everything too
Credit where credit is due. Writing a systemd script was so much easier than initd and it resolved so many race conditions and such
People just don't like change. It's the same when Wayland. People are pretending like x11 wasn't problematic ๐
The distros didn't choose this stuff because of business connections lol. And I'd love to see what red hat offered other distros to cause them to switch(I'm sure you have receipts)
Ubuntu even had upstart and even they dropped it eventually
I'm a user for about 20 years.
I must be lucky. I had no issues with pulseaudio. In fact I thought it was so wonderful how you could hear multiple applications at the same time!
I thought gnome 3 was really cool as well. I didn't use it as long as I did 2, but that's because I found out about tiling window management (and later scrolling window management). But I liked the design of Gnome 3, not sure why. Felt modern, like a bold step in a modern direction. ๐
Systemd I just have no feelings about. I'm not well-read about the drama or how or why it's a badly designed system. I don't write my own units or whatever. I just start/enable and stop services. ๐
But these were just examples. Maybe you mean more stuff have been bad coming from Redhat.
That was possible with ALSA and the "dmix" plugin years before pulseaudio came out.
Alright. Nothing I knew about at the time.
Still it worked really well for me, and the experience I have is basically that a working system (pulse) was replaced by another (pipe). Must've been lucky.
Yeah. I've been using Linux for at least 20 too
Things like pulse audio also exposed a lot of driver bugs in audio hardware. In fact, in Windows, I discovered my awe64 was massively slowing down my system
I suspect some people are confusing the issues with windows 7 too though, where some people also had audio issues initially
Ah, so they blamed pulse for driver and firmware bugs? I guess that happens easily.
Not all of when of course, but I seem to remember it was a factor. But it was so long ago now
Windows also had a lot of similar accusations at the time too
Interesting. Clearly a common thing, then. Thanks for sharing that!