Comment by nsbdhciebsbdhc
8 hours ago
Wanting stuff to work is a valid reason to not use AI for more sophisticated development projects. Having a computer that kernel panics once every three days is useless to me, even if it works for you.
8 hours ago
Wanting stuff to work is a valid reason to not use AI for more sophisticated development projects. Having a computer that kernel panics once every three days is useless to me, even if it works for you.
A kernel panic is the least of your worries with this hardware. Asahi had to introduce a custom daemon to avoid frying speakers. Apple doesn't need to care about making the hardware interfaces safe if they control the entire stack, so they don't, and expose dangerous capabilities to the OS.
There was a fun period of time where Boot Camp still existed, but Windows could fry the speakers because it didn't have any of macOS's thermal protection. I think this was after the 2016 redesigns, as I had a mid-2015 with no such issue.
Linux kernel itself is AI development friendly.
Some of us think that is a mistake.
Some people will always disagree with something. That's what's great about free software. There will probably be some Luddite anti AI Linux fork at some point.
Hmm very vague. "Some of us".
Do the massive amount of vulnerabilities not make you think twice?
At this point, I trust human code less than llm code. Design and architecture of the code still greatly benefit from a good human touch, but I'm not sure how long that will remain true.
https://www.phoronix.com/news/OpenAI-948-Linux-LPE-Bugs
1 reply →
That's not what they meant. It's AI friendly, not slop-friendly.
There's a reason no Omarchy patch of any kind has made it to the kernel list yet. I did personally look into some of their code and it is certified, hacked-togeter slop.
How do you define the difference between ai friendly and ai slop?
3 replies →