> We are completely overwhelmed, of course.
-
> We are completely overwhelmed, of course. The glimmer of hope is that we secured sufficient LLM budget and access (thank you Meta!) to run reviews with multiple frontier models on each patch. This eliminates some hallucinations.
jesus christ https://mastodon.catgirl.cloud/@lina/117130089920503564
@zzt "some hallucinations"
-
good thing the linux kernel has multiple frontier models, none of which are capable of generating a C compiler that fucking works
thank you Meta!
@zzt
They embraced, they extended, now comes the extinguishing (even if some of them believe it's extension) -
@zzt “we are drowning in slop, the solution is obviously more slop”
-
@raster I can not read the conversation here, thanks to @zzt for the block /s
I see that he enjoys the phrase "fucking slop", so you can point him and his fucking awful.systems to the open (non-blocked) anti-AI discussion linked below.
Alternatively, with less profanity:
― sloppy human systems.
https://www.reddit.com/r/freebsd/comments/1vtgx7t/antiai_open_source_has_an_enemy_in_common_but/
@grahamperrin take the block like a real poster and don't whine about it. (calling reddit “open” is a beautiful joke.)
-
@grahamperrin take the block like a real poster and don't whine about it. (calling reddit “open” is a beautiful joke.)
-
@grahamperrin please do not re-insert into the conversation people i deliberately removed in order to remove clutter in their threads, thanks.
i had a look at your timeline and now i do understand why people might not want to communicate with you; i just joined their number.
please do not reply, thanks in advance.
-
@grahamperrin please do not re-insert into the conversation people i deliberately removed in order to remove clutter in their threads, thanks.
i had a look at your timeline and now i do understand why people might not want to communicate with you; i just joined their number.
please do not reply, thanks in advance.
@mawhrin don't take an interest without properly knowing the facts and then feign disinterest.
-
@raster I can not read the conversation here, thanks to @zzt for the block /s
I see that he enjoys the phrase "fucking slop", so you can point him and his fucking awful.systems to the open (non-blocked) anti-AI discussion linked below.
Alternatively, with less profanity:
― sloppy human systems.
https://www.reddit.com/r/freebsd/comments/1vtgx7t/antiai_open_source_has_an_enemy_in_common_but/
@raster here's the less open public discussion, with greater engagement:
FreeBSD, AI, and LLMs
https://www.reddit.com/r/freebsd/comments/1vthk9s/freebsd_ai_and_llms/
― including a comment from a member of the FreeBSD Core Team.
-
-
@zzt "Are we the baddies" walked so that "Thank you Meta" could run.
-
but nah, I’m sure it’ll be fine, I keep seeing the take on here that somehow the kernel doesn’t matter at all for a desktop and nobody will notice when it breaks
you know, the code that literally all of your applications call into, that makes all your hardware work
the thing that was the point of being on linux at all
the kernel????
@zzt can’t wait for more and more events of “bizarre kernel bug fucks up physical hardware entirely”. if only there would be a way of like, not doing that. -
@zzt counterpoint: all elisp is holy
@hipsterelectron @zzt Eeeeh, I have written some that I would probably class as "unholy" (and, also, my partial implementation of elisp in Common Lisp was deeply unholy, but there to provide elisp shims for Climacs, don't think it ever got used and certainly never reached full parity).
-
@zzt can’t wait for more and more events of “bizarre kernel bug fucks up physical hardware entirely”. if only there would be a way of like, not doing that.
-
@hipsterelectron @zzt Eeeeh, I have written some that I would probably class as "unholy" (and, also, my partial implementation of elisp in Common Lisp was deeply unholy, but there to provide elisp shims for Climacs, don't think it ever got used and certainly never reached full parity).
-
@grahamperrin take the block like a real poster and don't whine about it. (calling reddit “open” is a beautiful joke.)
@mawhrin lol @ Reddit
To your point...
-
@hipsterelectron @zzt Sorry, Portable Hemlock, not Climacs.
-
@raster I can not read the conversation here, thanks to @zzt for the block /s
I see that he enjoys the phrase "fucking slop", so you can point him and his fucking awful.systems to the open (non-blocked) anti-AI discussion linked below.
Alternatively, with less profanity:
― sloppy human systems.
https://www.reddit.com/r/freebsd/comments/1vtgx7t/antiai_open_source_has_an_enemy_in_common_but/
@grahamperrin Perrin, your sentence structures & formatting, both with & without AI help, across both Mastodon & Reddit, read like pamphlets, with needless engagement-farming bells & whistles. Please give jumbled short quotaes, single-item link lists, & pointless hashtags for abstract concepts like "openness", a well-needed rest, & relearn basic communication skills before talking to others. You may find the quality of responses you'll receive will increase. #closedness #eatingpie #sawabirdtoday
-
I really liked having fully working linux systems for… like 7 out of the 30+ years I’ve been using this fucking thing
we even briefly got gaming before they decided to come and fuck it all up in exchange for money
@zzt So I realize that Linus saying "if you don't like AI, you can fork the kernel" was essentially a "go fuck yourself", but part of me wonders:
How much effort would it take to fork the Linux kernel, if you were willing to cut it down to the bare minimum needed to support a reasonable desktop/laptop environment?
eg, strip it back to x86-64 and maybe aarch64 only, one or a handful of the most critical filesystems, yeet half the subsystems and 90% of the drivers for simple maintainability reasons, and so on.
I'm sure the answer is still an unreasonable amount of work, but how unreasonable, is what I'm curious about. Because I'm kind of tempted to try...
-
@zzt So I realize that Linus saying "if you don't like AI, you can fork the kernel" was essentially a "go fuck yourself", but part of me wonders:
How much effort would it take to fork the Linux kernel, if you were willing to cut it down to the bare minimum needed to support a reasonable desktop/laptop environment?
eg, strip it back to x86-64 and maybe aarch64 only, one or a handful of the most critical filesystems, yeet half the subsystems and 90% of the drivers for simple maintainability reasons, and so on.
I'm sure the answer is still an unreasonable amount of work, but how unreasonable, is what I'm curious about. Because I'm kind of tempted to try...
If you have the time, I'd love to consumer-test your results!
-
@zzt So I realize that Linus saying "if you don't like AI, you can fork the kernel" was essentially a "go fuck yourself", but part of me wonders:
How much effort would it take to fork the Linux kernel, if you were willing to cut it down to the bare minimum needed to support a reasonable desktop/laptop environment?
eg, strip it back to x86-64 and maybe aarch64 only, one or a handful of the most critical filesystems, yeet half the subsystems and 90% of the drivers for simple maintainability reasons, and so on.
I'm sure the answer is still an unreasonable amount of work, but how unreasonable, is what I'm curious about. Because I'm kind of tempted to try...
@rachelplusplus
Lots
If you do it for yourself, that would be fine. If you want to keep it as a public distro, you still need to maintain lots of audio/video/network/usb/tb/sensors/storage/fingerprint/... drivers that can vary a lot even for the "reasonable" desktop and definitely laptop. Then occasionally you get hit by "now cameras use a special chip, hope you implemented it already". (And people will have issues with hardware you don't have)
@zzt -
P pelle@veganism.social shared this topic
️
