“nothing that can be done about this” says guy who caused this and derogatorily called anyone who doesn’t like it an SJW
-
@gooba42 @zzt Microkernels got a bad reputation by the microkernel folks doing them backwards. Putting sketchy hardware io stuff that actually needs to be isolated into the real core kernel but syscalls into unusably slow and misbehaving RPC Rube Goldberg machines.
A good microkernel is at its core the resource & state management (memory, scheduling entities, file handles, etc.) needed to implement POSIX with hardware drivers and filesystems in isolated userspace tasks.
@dalias @gooba42 @zzt Which seems to mirror the typical underlying architecture (CPU+Memory as core, rest being external, at least outside of MCUs/SoCs) + system constraints (like file handles managed in userspace sounds unnecessarily messy to deal with).
But well I've barely touched kernel-layer things so not sure how well that comparison holds up. -
“nothing that can be done about this” says guy who caused this and derogatorily called anyone who doesn’t like it an SJW
-
“nothing that can be done about this” says guy who caused this and derogatorily called anyone who doesn’t like it an SJW
before we could all imagine some nerd wrote each line and signed off on it.
blame hallucination 12,546.0003nobody knows what all is in it. passes benchmarks. ship it.
#kernel-is-ai-now #fuck-em-feed-em-fishheads -
-
-
-
-
when you’re a world class smart boy C expert but you fail to learn basic frontend Python so hard you get addicted to LLMs instead
“it’s just a tool and the future and you’re an SJW for not wanting it” torvalds screamed over the sound of rsync, a previously very stable C codebase that lots of infrastructure relies on, melting into vibed slop that can’t reliably do anything anymore
it’s fucking wild to see another foundational project break so hard a bunch of dependencies either dumped it or stayed on an old version and go “oh me too” and implement the exact same “tool” and development processes built around that “tool” and not see the train about to hit you when your releases start to look exactly like that other project’s releases
-
“it’s just a tool and the future and you’re an SJW for not wanting it” torvalds screamed over the sound of rsync, a previously very stable C codebase that lots of infrastructure relies on, melting into vibed slop that can’t reliably do anything anymore
it’s fucking wild to see another foundational project break so hard a bunch of dependencies either dumped it or stayed on an old version and go “oh me too” and implement the exact same “tool” and development processes built around that “tool” and not see the train about to hit you when your releases start to look exactly like that other project’s releases
@zzt these mfs need the humanities or jesus. though at this point im not sure what will redeem them
-
and again I’ll point out how fucking quick this shit is happening
torvalds posts a defense of AI slop in the kernel with a right-wing conspiracy theory as the reason
a bunch of other open source projects just go “well the kernel says it’s ok so we’re doing slop now”
barely a couple of weeks later the kernel is changing its release cadence and quality standards entirely and the man in charge is shrugging and literally going “what can you do”
you can cut the crap, asshole. it’s your literal job to cut the crap.
Finally! I always wanted Linux but the code is plagiarized from Linux! /s
-
“it’s just a tool and the future and you’re an SJW for not wanting it” torvalds screamed over the sound of rsync, a previously very stable C codebase that lots of infrastructure relies on, melting into vibed slop that can’t reliably do anything anymore
it’s fucking wild to see another foundational project break so hard a bunch of dependencies either dumped it or stayed on an old version and go “oh me too” and implement the exact same “tool” and development processes built around that “tool” and not see the train about to hit you when your releases start to look exactly like that other project’s releases
rsync in particular is insane to me because like it was finished, it didn't need updates, and it wasn't getting any because it was finished, but the maintainer who had given it away to someone else because of burnout for some reason decided to take it back and has now ruined it completely with gibberish code from the robot.
-
@TheOneDoc @zzt I would be surprised, honestly, if he were financially in a place where he could not afford to stop working for a paycheck. Then again, people surprise me all the time.
-
@TheOneDoc @zzt or alternatively, wielding Linux contributor status as a union membership and challenging employers to go fork it if they don’t like it
-
@TheOneDoc @zzt i disagree. The big contributors want access to steering and influence in big picture changes. There is little reason for them to care if they allow whatever flavor of AI is their (dead) horse atm.
The worst that could happen to MS, G, and AMZN is if Linux were to tighten license conditions on the kernel -
rsync in particular is insane to me because like it was finished, it didn't need updates, and it wasn't getting any because it was finished, but the maintainer who had given it away to someone else because of burnout for some reason decided to take it back and has now ruined it completely with gibberish code from the robot.
@daemonspudguy @zzt Number (of new lines of code) go up.
-
oh hey, some of you have seen this before but look at torvalds’ prior work before shoving LLMs forcefully into the workflow of the kernel:
https://infosec.exchange/@atax1a/115867354992858960
it’s a fucking Python data visualizer tool that you or I could have written in a day, but torvalds decided Python wasn’t a worthy language for him to learn so he used an LLM instead
and this wasn’t his first time fucking with the things, but this was his last project before he decided to go all-in
somehow an LLM doing a shit Python data visualization tool for one of his hobbies convinced him that LLMs must be really good at the type of low-level C the kernel is written in
that’s all the evidence this mid little fucker needed to assert it as fact
@zzt I remember that incident. I heard so much that I was overreacting and how this is actually a good use of LLMs and he knows never to use it in the kernel.
Whelp.
-
and again I’ll point out how fucking quick this shit is happening
torvalds posts a defense of AI slop in the kernel with a right-wing conspiracy theory as the reason
a bunch of other open source projects just go “well the kernel says it’s ok so we’re doing slop now”
barely a couple of weeks later the kernel is changing its release cadence and quality standards entirely and the man in charge is shrugging and literally going “what can you do”
you can cut the crap, asshole. it’s your literal job to cut the crap.
@zzt Hey, Linus, I think this qualifies as you having been hit by a bus.
I just hope the next guy isn't as bad. (yes, the contingency has been planned for, so I'm not so optimistic on this front---chosen successors tend to hew closely to their predecessor's worldview)
-
“nothing that can be done about this” says guy who caused this and derogatorily called anyone who doesn’t like it an SJW
@zzt He needs a fucking slap
-
@TheOneDoc @zzt i disagree. The big contributors want access to steering and influence in big picture changes. There is little reason for them to care if they allow whatever flavor of AI is their (dead) horse atm.
The worst that could happen to MS, G, and AMZN is if Linux were to tighten license conditions on the kernelHappy willful ignorants blind themselves day!
-
“it’s just a tool and the future and you’re an SJW for not wanting it” torvalds screamed over the sound of rsync, a previously very stable C codebase that lots of infrastructure relies on, melting into vibed slop that can’t reliably do anything anymore
it’s fucking wild to see another foundational project break so hard a bunch of dependencies either dumped it or stayed on an old version and go “oh me too” and implement the exact same “tool” and development processes built around that “tool” and not see the train about to hit you when your releases start to look exactly like that other project’s releases
@zzt i think we just get more and more proofs that LLMs are incredibly addictive, and that you should never use them even just as a test on some dump code because you'll quickly become so hooked you'd willingly become the infection vector for the rest of your projects too.
