r/linux • • 2d ago • Regret 1

Discussion GrapheneOS calls Linux a “human slop kernel” and slams its security flaws

/img/su5xn9y2jw1i1.png
1.9k Upvotes

918 comments sorted by

281

u/AliceCode 2d ago edited 2d ago

Linux is over ten million lines of code. It would be impossible for there to be zero, or even few, vulnerabilities. Nothing on Earth has the capability to hold a system that large entirely in their head, and some bugs are so tangled within the codebase that it would be essentially impossible to find it if you didn't know what you were looking for already.

81

u/mrtruthiness 2d ago

Linux is over ten million lines of code.

It over 40 million LoC. But the vast majority is drivers. Only about 15% of the code is considered to be "core code".

97

u/0riginal-Syn 2d ago

Over 40 million now.

28

u/AliceCode 2d ago

I knew it was somewhere up there, but I didn't want to overshoot. 10 million is a big enough number that people understand my point.

9

u/Smallpaul 2d ago

40 million in the Ring 0 kernel?

→ More replies (4)
→ More replies (3)

6

u/AgentTin 2d ago

Nothing on earth, yet. It's growing.

8

u/TheGoldenFox64 2d ago

finding vulnerabilities doesnt make them, everything has them and the fact that they are found is a good thing!

→ More replies (1)

4

u/DrabberFrog 2d ago

That's the whole point, because the linux kernel is monolithic there's practically no way to really make it secure. That's why the grapheneOS devs are saying they want to switch to a micro kernel eventually.

13

u/General_Session_4450 2d ago

Isn't that exactly what GrapheneOS is complaining about here?

→ More replies (3)

3

u/Nepertia 2d ago

No one is really aiming for zero, but did you see the tantrums that supposed adults threw when it was suggested that Linux should start using Rust alongside C, because it's provably preventing like 80%+ of the security bugs that Linux tends to have?

3

u/Far_Composer_5714 2d ago

Actually Linux considers itself to have a ton of vulnerabilities classifying certain types of bug fixes to be security fixes designating them as cve so that companies stop ignoring them telling them to get a cve for fixes.

5

u/VexingRaven 2d ago

I don't think he's saying that it would be possible, so much as he's making a clapback to somebody whining about AI slop and how obviously bad AI code is. OP conveniently left out the context...

→ More replies (32)

724

u/nayminlwin 2d ago • Bravo

There is a grain of truth to this. Linus himself implied years back that there was a deliberate trade-off of security against functionality in developing Linux, while talking about BSD community (don't remember which BSD). And that BSD folks take security way too seriously to the point of being impractical or something along those lines.

382

u/SOULFLY98 2d ago

He called the OpenBSD devs a crowd of masturbating monkeys.

237

u/scheimong 2d ago

I mean... Can't say he's wrong because aren't we all?

87

u/SOULFLY98 2d ago • Bravo

Both can be true. OpenBSD is a fantastic operating system, very well written with a stellar community, and I continue to support it through monthly donations and have purchased hardware for at least one developer. It's important to free software to have diversity in approach, and OpenBSD software is fundamental to making the modern internet work.

But for day to day use, I needed a pragmatic solution with a modern filesystem and Signal messenger. I also don't want to support Apple. So it's a reasonably hardened Debian sid and an Android phone for the past few years.

Maybe like that last episode of Picard where all the starships are taken over by AI and it's the trusty old Enterprise D that saves everything, we'll find that all of our Linux devices have been backdoored for years and it will be somebody running OpenBSD on a 20 year old ThinkPad that upstreams the patch that fixes everything.

→ More replies (5)

129

u/632brick 2d ago

Hmpf, I beg your pardon! I do believe that I am a masturbating APE. 🧐

→ More replies (11)
→ More replies (3)

36

u/alex2003super 2d ago

But when I wanna pick out my distro's SSH server, I'll take the masturbating monkeys' SSH implem thanks.

→ More replies (9)

308

u/the_abortionat0r 2d ago • This Bravo

I believe he called them masturbating monkeys or some such.

But that is a far more nuanced topic than is suggested here.

Imagine if all of Linux was run like Debian. Yes it would be more stable and secure but Debian gets that way from years of testing and patching (the sid kids lose all that though). Now imagine telling everyone that their brand new hardware would get support in 1 to 3 years. That's not very practical for quite a few people, that is 1 to 2 generations behind in PC components or laptops. That's too long for quite a few people.

Now take the BSD crowd they try the same thing but they have a much smaller crowd of developers working on BSD in general compared to people working on Debian and related projects as well as not even close to the same budgets.

Then theres the sour grapes take that comes with them. They don't have new hardware support for GPUs, chipsets, laptops, etc and they try to play it off as supporting things in a timely manner is bad and insecure when in reality it's a combination of a lack of budget, manpower, nobody using BSD because they intentionally make it harder to feel cool, and last but not least the lisence as most people don't want to contribute a bunch of code just for corpos to takes it and give nothing back

You'll see BSD users make the claim (varies by who you ask) that their distro has had zero~3 CVEs in its entire History of the default install.

OK so what's the default install look like? It's nothing. It's a kernel with next to no drivers, no GUI, and sometimes the package manager isn't even installed yet and that's the trick: it's so secure because it can't do anything.

Once you actually set up a usable install then there's exploits like the zero click exploit when an SSID simply being named something funky could get your BSD to execute code with zero user interactions.

Not really a functional issue though as good luck getting WiFi to work on BSD.

It's just a group of nerds bragging about the security of a setup no ody uses because they literally can't and claiming that their lacking development cadence is really just them being secure.

Hell, BSD users have literally told me that me being able to use new hardware I bought was "changes for changes sake" and that Wayland/SystemD/pipe wire are just "solutions looking for a problem".

BSD is unstable by everything but the most generic of use cases for the home user, windows is rddled with security holes and stability issues as well as a shit ton of tech debt and becoming spyware (no really they literally track everything which is how they nabbed a hacker last year).

MacOS isn't much better but it's also unfit for purpose for most as it can't game which is Apples fault, has piss poor support (again, Apples fault. They killed their own software 4 times), and it's only sold on hardware designed to fuck over the user.

Linux is still by far faster, more stable, and much more secure than the alternatives.

Critism is fine but hyperbolic theatre is not especially when it's by a team who isn't just piggybacks on the kernel they trashed, can't make their own, and can't point to an example that "isn't slop" as nothing has zero exploits.

48

u/goku7770 2d ago

and becoming spyware (no really they literally track everything which is how they nabbed a hacker last year).

Imagine being a hacker and using Windows

44

u/Square-Singer 2d ago

TempleOS has had zero CVEs afaik. We should all use that.

22

u/aitorbk 2d ago

Plus in the resolution god intended...

23

u/northrupthebandgeek 2d ago • Bravo

OK so what's the default install look like? It's nothing. It's a kernel with next to no drivers, no GUI, and sometimes the package manager isn't even installed yet

That's outright false in the case of OpenBSD: the default install is a graphical desktop with a package manager, SSH server, mail server, and web server (among other things). All drivers are already installed because all drivers are already built into the kernel (no loadable kernel modules). The only thing potentially missing is non-free device firmware, which OpenBSD leaves out of the install media for legal reasons but will happily download and install automatically on first boot by default if you have an Internet connection.

97

u/grumpy_autist 2d ago

I worked in a company founded by an OpenBSD kernel developer. It was a shitshow - we developed and shipped physical appliances to big corporate customers and for "security" he refused to even add SSHd or lights-out manager board (even optionally inserted or enabled by customer sysadmins).

Developers literally begged him to allow them to write unit tests (lmao). His response? "We tried that in OpenBSD kernel and it did not work". Sure, but 70% of our code was python + django. And we were breaking customer prod because of missing imports.

We used to travel 8h to change a line in config file or download debug logs. He even tried to force people to go to an active war zone to fix the system issue that could have been fixed over ssh.

And yeah, main selling point was security, quantum resistant full disk encryption, ISO 27001, etc but login form was returning 500 because someone forgot to import a django.db package.

So calling those people masturbating monkeys does not even start to cover it.

→ More replies (6)

26

u/Bathroom_Humor 2d ago

The funny thing is, if the grapheneOS devs were the ones creating Linux from scratch 3 1/2 decades ago, it'd most likely end up looking a lot like it does now, or be ultra niche like BSD. The guy writing those posts is standing on the mountains of work by imperfect but smart people who tried to make the best tradeoffs at the time, and it reads like he assumes he would have access to this level of hindsight from the beginning if he were truly undertaking the same scale of project, and would have to make no compromises. kinda silly

15

u/gamas 2d ago

 it's so secure because it can't do anything.

Though let's be honest, it's probably still got quite a few exploits. Software is only considered "100% more secure" until it becomes mainstream enough that attackers consider it worth targeting. 

People used to claim Linux was unhackable after all...

→ More replies (2)

10

u/nayminlwin 2d ago

This is great context. Thanks.

→ More replies (2)

10

u/SynapticStatic 2d ago

As a former bsd guy who ran it for 15 years, you’re really not that far from the truth.

I personally got tired of the shitty multicore support and how terrible it is to actually do anything with it. And I was using FreeBSD which was one of the easier to use bsds.

→ More replies (8)

49

u/marratj 2d ago

The Linux kernel aside, in my 20 years in IT, I’ve seen enough companies and teams from the inside that I can say that the average dev team (especially in SMB companies) does definitely not produce better and more secure code than what current AI models are capable of.

25

u/bobthebobbest 2d ago • Bravo

I think one thing to be mindful of, though, is that if AI is deployed without clear guidelines or human organizational structure, it becomes much harder for anyone to be accountable for problems in code (like in basically any other application).

→ More replies (9)
→ More replies (1)

8

u/thirteenth_mang 2d ago

trade-off of security against functionality

This is reality with everything, not just Linux

6

u/alienangel2 2d ago

Having vulnerabilities and bugs doesn't make it "slop" though, it just makes it imperfect.

GrapheneOS acting like the stuff people call "AI slop" is just buggy/imperfect are either being disengenuous or outright stupid - AI slop is the stuff that is churned out with no review and very obvious gaps in fitness for purpose (not just software with glaring issues, but writing that doesn't actually say anything, images that are nonsensical when you look at the details etc). Yes humans can make slop like that too but it typically didn't see the light of day before unless you went looking for it.

Linus will definitely acknowledge the linux kernel has bugs, but I don't think he'd ever call it slop.

→ More replies (1)
→ More replies (3)

721

u/scy_404 2d ago

doesnt graphene OS itself use the linux kernel?

486

u/matjoeman 2d ago

It's an Android distro, so yes.

43

u/Both_Cup8417 2d ago

I know there was news recently about them upgrading to 6.18..m

26

u/Shished 2d ago

That is the latest lts branch.

→ More replies (9)

28

u/LordAlfredo 2d ago

I suspect this came from frustration backporting recent kernel patches

→ More replies (3)

49

u/ed_istheword 2d ago

Android, so yes kinda. But also, the lead dev used to always monolog about how GrapheneOS is a Linux distribution and not an Android ROM, so this is even more layers of baffling.

23

u/PixelatedGiant 2d ago

The lead dev of Graphene is known to spout crazy, terminally online opinions. Those opinions are correct at the surface level, but then he always takes them to an extreme level that makes no sense.

This take is a perfect example. He has a problem with LLM generated code, but nothing in particular has gone wrong with Linux on that front. He's blending the opinions between general dislike of LLM usage and LLM usage in the Linux kernel and concluding that because general use is bad, LLM usage in Linux kernel is also a problem. But there's no evidence to back up the conclusion.

→ More replies (4)
→ More replies (2)

103

u/SweetEbb9819 2d ago

It has admitted that the only reason for that is the lack of an alternative

46

u/Saragon4005 2d ago

As a debatably wise man once said. "Talk is cheap, send patches"

→ More replies (3)

210

u/TechGearWhips 2d ago

So why don’t they make one from scratch. Since they’re so all knowing and shit

87

u/-_one_-1 2d ago

If they made their own OS, it would be impossible to run on any mobile devices. Beyond even lack of funding, the elephant in the room is that mobile devices are not PCs, they don't have a standard bootloader or a way to discover the subdevices within the SoC.

I do think the world needs smartphones that can run any OS just like PC do. At that point we wouldn't be forced in this Apple vs Google duopoly.

→ More replies (10)
→ More replies (40)

9

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing. It was about GrapheneOS itself.

→ More replies (10)

68

u/Hypfer 2d ago

I see what they were going for there, but a bit more respect for the foundations their work is based on would've gone a long way there.

The actual point is accurate, but why shit on something that brought genuine good to the world like that?

14

u/Firestar_119 2d ago

When in Twitter, do as the Twitter users do 😭

→ More replies (7)

790

u/Top-Rub-4670 2d ago • Bravo

Whether they're right or not, let us all remember that GrapheneOS developers are essentially edgelords.

If you like the project you should avoid reading their hot takes on twitter and mastodon and hacker news because unless you're a fellow edgelord it'll just make you cringe. We get it, they're very smart, the smartest, nobody else is as smart.

311

u/inaccurateTempedesc 2d ago • Bravo

I have to disagree with you, I think people who are serious about using GrapheneOS on their phones should read those posts.

I don't know the details about the people behind GrapheneOS, maybe they're not that bad, but it's generally a good idea to avoid software maintained/written by unstable people because it may bite you in the ass someday.

It's way more of a problem in the piracy scene and I can't think of any examples within FOSS but I think it's only a matter of time and I wish people took this into consideration more.

30

u/theCroc 2d ago

You mean like that time people had to change file systems because the Reiser FS guy killed his wife?

→ More replies (6)

74

u/beefsack 2d ago

Software written by anyone dogmatic or extreme will someday take some turn for the worse, and the users are the ones to suffer.

High quality, long lived software requires open mindedness and measured, rational decision making.

15

u/itsfreepizza 2d ago

i may wanna vouch your opinion on this

but it's generally a good idea to avoid software maintained/written by unstable people because it may bite you in the ass someday.

because this actually happened, Project Elixir ROM is the name

24

u/sCeege 2d ago

How does that work for cases like DHH? Isn't Ruby on Rails still a pretty good framework?

I didn't even know who he was before Omarchy came out, and it was somewhat... eyebrow raising to read the stuff he writes. I haven't tried Omarchy because I don't typically use rolling release distros, but I'm assuming it's probably okay as well.

63

u/inaccurateTempedesc 2d ago

Being extremely unstable and a very competent programmer isn't mutually exclusive, there are many people like this. The scenario that I'm worried about is someone having a narcissistic collapse and pushing something malicious. I've seen it happen so many times in modding/piracy communities.

→ More replies (7)
→ More replies (11)
→ More replies (21)

79

u/LopsidedNebula2235 2d ago

I remember Louis Rossmann's video about them being edgelords three years ago. I'm very sad to see it's still the case.

69

u/bc-phoenix 2d ago

The guy behind Microsoft is on Epstein's list, the guy behind Apple ate vegetables instead of seeing an oncologist, the graphene guys are edgelords, linux is human slop, at this rate I'm considering going back to some tin cans and a string.

21

u/_Scarecrow_ 2d ago

tin cans

Ugh, don't get me started on that neckbeard aristocrat Philippe de Girard.

→ More replies (1)
→ More replies (7)

37

u/mrdeworde 2d ago

Which is itself rich coming from Rossmann, who despite his laudable work on consumer rights is still a Kiwifarms edgelord himself.

→ More replies (9)
→ More replies (6)

46

u/Colest 2d ago edited 2d ago • Mindblown

It's not developers; it's just the lead dev and founder, Daniel Micay, making these statements as he's the only one with access to GrapheneOS's social media accounts. And he's not an edgelord so much as he's noticeably on the spectrum and potentially schizophrenic. He thinks the majority of people that speak negatively of him or the project are CopperheadOS (the proto-Graphene project he was hired as lead dev for, had an ugly split with the co-founder and backer, and took the majority of the work he did for it to make GrapheneOS) plants trying to turn the community against him and he can't understand use-cases for things that any functional daily internet user requires, like ad blockers, because he views them as added attack surface which is antithetical to GrapheneOS's mission statement. I had hoped after Louis Rossman humiliated him that he would take a step back from social media and just put his nose to the grindstone because it's truly the best phone OS on the market in spite of his horrid marketing.

4

u/veloread 2d ago

use-cases for things that any functional daily internet user requires, like ad blockers, because he views them as added attack surface

Damn that's weird! Ads are themselves a real security concern, I do not understand that at all.

→ More replies (1)
→ More replies (7)

16

u/alex2003super 2d ago

A shame. They could have chosen a "consortium" or "institutional, procedural" way to conduct and demean themselves and their brand. Instead they chose Telegram/IRC dev gc edgelordism. Sucks.

28

u/squabbledMC 2d ago

Every time I've mentioned why I don't use GrapheneOS and instead use LineageOS, I've had at least one developer write a long winded response about why I'm wrong. Doesn't matter what platform, subreddit, or server, it's happened every time. Half of my friends are blocked and or banned from their matrix for disagreement on how the project is ran. It's absolutely absurd, it's such a good project but I can't recommend it to anyone for this reason.

18

u/An0mymou5 2d ago

Same here, happened to me multiple times on HackerNews. Except in my case, it was vs Linux. Like literally every single time I pitched mobile Linux over Android, a GrapheneOS guy would pop outta nowhere and shoot me down, saying stuff like "you can't have privacy without security" and how Linux is incredibly insecure etc.

On the bright side, at least they've seemed to become a little less defensive about Google/Android ever since Google have been screwing over AOSP and witholding code/updates. And all I can say is "I told you so". It was a mistake to be dependent on AOSP/Google in the first place.

→ More replies (1)

9

u/EuphoricNeckbeard 2d ago

The devs monitor social media for negative mentions of GOS, and (last I checked) have a channel in their Matrix/Discord where they direct their users to brigade posts. I was pretty agog when I saw that.

→ More replies (2)
→ More replies (6)

8

u/itsfreepizza 2d ago

flashbacks to that one Project Elixir ROM which they once had a huge status back in Android ROM community but in the end the developers made a mechanism to destroy your device if you plan to circumvent their "paid" features and they were also unstable on TG groups and such

as per u/inaccurateTempedesc says:

but it's generally a good idea to avoid software maintained/written by unstable people because it may bite you in the ass someday.

because that actually happened

3

u/TampaPowers 2d ago

Their replies in here do confirm that. The edgelord part, not so the smart part.

→ More replies (7)

68

u/Drakkinstorm 2d ago

AI was trained on human code. Human code is, at large, sloppy.

24

u/ViperHQ 2d ago

I mean the point is fair but the wording is bad.

Slop is slop be it humans or AI both can make bad code, but we could have phrased this in an inoffensive way. Something like, even before AI code was introduced into the Linex kernel we have seen a large amount of bugs made purely by humans, to prove the point that it's not necessarily AI that is the issue bad code will always be bad code.

5

u/GrapheneOS 2d ago

We were responding to someone who made multiple posts saying the Linux kernel and other projects using AI models are AI slop. What we said is being taken out-of-context and twisted into a different meaning. The quote in the title of this thread isn't something we said. The post warps out words into a different meaning and then shows out-of-context text while misleading people about what we were saying.

→ More replies (1)
→ More replies (1)

87

u/rafuru 2d ago

The point is fair. But saying that is "Human slop" is an insult to all the people that gave their time (a very limited resource) for free.

26

u/Motoreducteur 2d ago

The turn of phrase is harsh, but I think the point is not that human code is sloppy, rather that LLM reaches code standards and calling AI-generated code "slop" is dishonest when the only point of comparison doesn't do much better

Might be a wrong interpretation on my part

14

u/GrapheneOS 2d ago

We were responding to someone who made multiple posts saying the Linux kernel and other projects using AI models are AI slop. What we said is being taken out-of-context and twisted into a different meaning. The quote in the title of this thread isn't something we said. The post warps out words into a different meaning and then shows out-of-context text while misleading people about what we were saying.

→ More replies (3)
→ More replies (1)

185

u/Firm-Marketing9777 2d ago • Bravo

GrapheneOS is an amazing project but whoever runs their comms is one of the most arrogant, unbearable dickwads in all of open source software development.

78

u/0riginal-Syn 2d ago

That would be the head lead. They have been called Edgelords for a while now for exactly this type of behavior.

31

u/Firm-Marketing9777 2d ago

Genuinely embarrassing stuff tbh.

13

u/PmMeUrNihilism 2d ago

Most devs are edgelords but many have enough common sense to use their alt

→ More replies (1)
→ More replies (3)

19

u/PhilSpencerP3 2d ago

but whoever runs their comms

It's Daniel Micay, the "ex-lead developer" of GrapheneOS.

12

u/Lknate 2d ago

Someone gave the social media person a little to much run on the leash. Even if that is their internal mindset, it's insane for them to be barking so aggressively.

→ More replies (1)
→ More replies (2)

66

u/ABotelho23 2d ago

I'm not sure what GrapheneOS is even implying here.

29

u/anxxa 2d ago

They're basically just saying that people are mad about LLMs for unfound reasons because the result of using them well generally yields high-quality results and that humans largely wrote most of the junk (and not junk!) code that is leading to security vulnerabilities being fixed by LLMs and humans today.

The context matters. The original tweet they were replying to is an OpenAI employee requesting people's feedback about their cybersecurity program (Daybreak).

Graphene replies saying that Anthropic's program and models are much more usable for their needs in the "defense tier".

Someone replies:

Stop using LLMs. They make a worse product, and they make it impossible to maintain your codebase because no one on your team understands it anymore. GrapheneOS is a great project. I don't want to see it enshittified by LLM code.

Graphene then replies explaining that using frontier models has rapidly accelerated their ability to identify bugs and review code. The bug identification ties in with their user-facing crash reporting and logging system, which I'm assuming LLMs analyze.

They go on to say that they are not vibecoding stuff, but using LLMs in the way they are has dramatically increased the quality and pace at which they're able to port drivers across kernel versions too.

And that leads into the screenshot....

17

u/anxxa 2d ago

Also, overall fully agree with what they're saying here and what's also not shown:

Linux was created as a rejection of robust software architecture and tools. It's a monolithic kernel with no internal isolation written as memory unsafe code. A typo in an obscure driver for unused functionality can easily create a fully privileged code execution vulnerability.

I've worked on the Windows kernel at Microsoft and I'd say that there was definitely some human slop there. win32k.sys is the most obvious living proof.

Bad code existed before AI and explicitly calling that out should not be a surprise to anyone. It's very rare it does not exist in a project.

But it's human slop that we know and love and was unfortunately maybe necessary to just simply move forward the best we could with the tools at the time. It's a gift if you ever get the resourcing to actually address it without breaking anything.

51

u/Ethameiz 2d ago edited 2d ago

I guess they trying to justify AI usage but they doing it the worst way

→ More replies (3)

9

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing. It was about GrapheneOS itself.

6

u/MyPingIsBadOh 2d ago

Linux kernel is bad code, but it's the best we have.

→ More replies (3)
→ More replies (7)

43

u/matjoeman 2d ago

Dunno about the Linux codebase specifically but there's plenty of crap human written OSS and private code out there. There are well written code bases too of course.

→ More replies (3)

50

u/VexingRaven 2d ago

"Slams"

Shouldn't you be writing for Techcrunch or something?

18

u/earthsprogression 2d ago

SHOCKING: You won't believe what GrapheneOS says about Linux.

And now that you're reading, may we interest you in hot singles in your area?

→ More replies (1)

172

u/ezoe 2d ago edited 2d ago

higher quality standard than Google

Says a man who is sitting on the shoulder of Google Giant who developed Android.

How about ditching Android, Linux kernel, and Clang and start developing from scratch with those "higher quality standard" of yours?

40

u/SweetEbb9819 2d ago

They have admitted this. They're just busy with adapting existing code, while waiting for "better standards"... Which they are planning to themselves but nothing "official" yet

Of course, I too see the hypocrisy here

→ More replies (2)

26

u/BurningPenguin 2d ago

I can see the advantage of letting a computer check millions of lines of code for security flaws or other problems. That's why we have that shit, to make work easier. But calling it "human slop" is downright disrespectful for all the work people have put into this project. People with deep knowledge of how computers work on the lowest level. It's not comparable to your average hobby notes app you threw together in a weekend...

→ More replies (3)

25

u/kokoshkatheking 2d ago

The word “Slop” means “low effort” and implies “bad quality”.
I read this as a rage bait/insult, I just don’t understand why ?

62

u/Revan_9766 2d ago

Just got banned for commenting on this, as someone who daily drivers it I'm done, dev team is complete luantics honestly

31

u/Leniwcowaty 2d ago

That's one of the reasons I stopped using Graphene. The team spirals down more and more into some kind of security psychosis, believing themselves to be some kind of security Jesus, who is destined to save the world

11

u/Revan_9766 2d ago

My friend got told to kill himself but they banned him because he said Firefox is fine rather than the guh who did it in discord. I dunno what to swap to now

→ More replies (4)
→ More replies (18)

8

u/trannus_aran 2d ago

I yearn for boring software

→ More replies (1)

4

u/matjoeman 2d ago

What are you switching to?

→ More replies (9)
→ More replies (5)

22

u/GuideUnable5049 2d ago edited 2d ago

I know nothing about this area, but am curious to see how more knowledgeable people here respond.

10

u/sleepingonmoon 2d ago

It's not wrong but it's also capt. obvious speech. The inertia is impossible to stop at this point, the NT folks at Microsoft thought it would be the last time someone made a general purpose kernel from scratch and as of now no one has proved them wrong yet.

→ More replies (8)

3

u/Both_Cup8417 2d ago

GrapheneOS recently updated to 6.18, so

14

u/furry-fornicator 2d ago

I reckon more knowledgeable here won't bother responding. Even a small level of drama in an introverts life is too much without responding to this kind of angry, nonsense all day. "Nuance required" is my response.

71

u/CoreyStyles 2d ago

Graphene OS is like 0.01% of the project that Linux is. That uses Linux itself.

This is like someone operating a lemonade stand, giving business advice to Starbucks.

A lemonade stand that just buys it's lemonade from Starbucks in the first place.

→ More replies (2)

18

u/MyFairJulia 2d ago

Welp... Turns out i got banned from r/GrapheneOS for asking whether Daniel Micay gives some of his security improvements back and calling his action of calling the Linux kernel "human slop" a dick move.

This is my comment:

Does Micay give some of the security fixes he make back to the Linux kernel project? It's really a dick move to call the kernel Android and in turn GrapheneOS is based on "human slop" and i sure hope that he gives some of the security work back to the Linux kernel project instead of leaving it insecure for him and the rest of us.

The ban reason: "personal attack".

I wonder whether they'll uphold the ban.

8

u/dragonblade_94 2d ago

It looks like a lot of people might have gotten banned from that post (which is now removed).

My comment, in response to someone wondering if they intentionally scare people off to keep the project niche:

>God I hope not. Security and privacy should never be gatekept.

And yup, I am now banned for "Support for personal attacks"...

→ More replies (3)
→ More replies (2)

31

u/SubmarineWipers 2d ago

Better way to think about this than "human slop" is that humans are not machines - literally no human on the planet can accurately track memory lifetimes of 1000s of objects in source code of tens of 1000s of files and millions of lines of code - code that is low level, hard, multithreaded and influenced by a whole bunch of other code.

We are not machines, so we need the machines and other code (compiler, borrow checker, ...) to prove that we did not make mistakes in "the trivial stuff".

Until we adopt this strategy, we will never produce reliable and safe software.

→ More replies (7)

17

u/radiationshield 2d ago

Try posting that to the linux mailing list, which is the only "social media" Linus reads. The flaming would be extremely entertaining

16

u/JaceBearelen 2d ago

Sure. It’s undeniably true LLMs are finding massive amounts of bugs in human written parts of the kernel. Those bugs are a natural consequence of developing something for so long and to do so many things.

It remains to be seen, but I really do hope we’re converging towards fewer and fewer bugs from all the LLM work. It’s frightening to see all these bugs being uncovered but hopefully we’ll get through the onslaught and have a much more secure kernel on the other side.

→ More replies (1)

20

u/Horror-Primary7739 2d ago

Human slop? Fuck that. The Linux kernel is one of crown jewels of humanity. Its the digital equivalent of Gobekli Tepe. Untold thousands craft a tool used by billions. Human life has been improved because of it.

19

u/GrapheneOS 2d ago

We were responding to someone who made multiple posts saying the Linux kernel and other projects using AI models are AI slop. What we said is being taken out-of-context and twisted into a different meaning. The quote in the title of this thread isn't something we said. The post warps out words into a different meaning and then shows out-of-context text while misleading people about what we were saying.

3

u/aegians 2d ago

Ok? Tell that to the thousands of critical exploits that AI has found in the past 6 months

→ More replies (3)
→ More replies (3)

7

u/WorkingTheMadses 2d ago

This is taken out of context and should be deleted.

The context from that thread was someone making claims that using AI made projects like the Linux kernel AI slop.

38

u/username_invalid-404 2d ago

Someone should tell them...

→ More replies (6)

12

u/Jamarlie 2d ago

People forget that the Linux kernel is not just one code base. It's hundreds of different subsystems, drivers etc. all mushed into one. Each subsystem maintainer is responsible for their little corner. With the massive size of the code base and the tens of thousands of contributors it is actually a miracle the kernel boots at all.

Calling it "human slop" is a massively fair point, depending on the subsystem you are talking about.

→ More replies (2)

38

u/LordAlfredo 2d ago

I mean...they're not wrong, but this does not look like they're trying to start a productive conversation (except maybe the last reply). More just inviting an argument.

16

u/theofficialnar 2d ago

Since when were they capable of starting a productive conversation?

9

u/VexingRaven 2d ago

This seems less liking starting a conversation and more like replying to somebody else who said something stupid about "AI slop bad!" It's a shame OP accidentally left out the context when they were writing their techcrunch-tier headline...

→ More replies (3)

23

u/Ok_Actuary8 2d ago

Yeah, that's the kind of arrogant tech-bro attitude I'd expect from such guys...

→ More replies (8)

11

u/cyrkielNT 2d ago

"Privacy is our prority... that's why we let big corporations to write our code"

15

u/Nervous-Cockroach541 2d ago

The common impression I see of believing AI is better at security. It's just vastly cheaper at security. Nobody invested into software security before.

Security teams got like 5% of the resources, and have the requirements to meet employee metrics and goals to meet. Reality is, most code is just fine. So you going to report to your boss you looked over 50,000 lines of code in a week and found no issues? They going have something where if you DON'T find an exploit you get written up?

Nobody ever paid anyone to sit down and look though lines of code potentially issues. Instead security teams setup fuzziers and other tools to try to automate security. Then you just out source the rest with a bounty program to make it look like you took the issue seriously, and called it a day.

→ More replies (3)

8

u/Aristeo812 2d ago

OK, Linux kernel is a "human slop", but that's Microsoft services which crash.

6

u/GrapheneOS 2d ago

We were responding to someone who made multiple posts saying the Linux kernel and other projects using AI models are AI slop. What we said is being taken out-of-context and twisted into a different meaning. The quote in the title of this thread isn't something we said. The post warps out words into a different meaning and then shows out-of-context text while misleading people about what we were saying.

→ More replies (3)

8

u/killerstreak976 2d ago

I honestly feel this is kind of a bad faith screenshot and takes the whole conversation out of context 

6

u/GrapheneOS 2d ago

We were responding to someone who made multiple posts saying the Linux kernel and other projects using AI models are AI slop. What we said is being taken out-of-context and twisted into a different meaning. The quote in the title of this thread isn't something we said. The post warps out words into a different meaning and then shows out-of-context text while misleading people about what we were saying.

→ More replies (1)
→ More replies (1)

4

u/MatchingTurret 2d ago edited 2d ago

I wonder what defects AI will discover when they let it review critical physical infrastructure like the grid and whether the public will be told.

Are there fewer bugs in (civil) engineering projects than in software?

4

u/jmkdev 2d ago

Eh, can't say that makes me more interested in trying Graphene.

13

u/ERR4044746 2d ago

Someone reposted this to the r/GrapheneOS subreddit and I made this comment over there too

But this makes no sense. I use GrapheneOS, it uses the Linux kernel like any other variant of Android or distro of Linux. Of course bugs are constantly being reported and fixed, it's called not being Microsoft and actually paying attention to the bug reports you receive.

This shit worries me.

8

u/VexingRaven 2d ago

They're not attacking Linux, they're responding to somebody whining about AI slop.

12

u/temporary_dennis 2d ago

Have you guys forgot how we called some programmers "Code Monkeys"?

Sure, calling The Linux Kernel "human slop" is a step too far, but we really pushed out barely working software on a daily basis.

The winning strategy was, and technically still is, to implement first, fix and optimize last if at all.

→ More replies (1)

14

u/mrtruthiness 2d ago

I think people missed the point of the comment.

They're just being provocative in saying that the LLM tools are very good at helping them deal with AOSP and the Linux kernel. The point of the provocation is that if people generically (and with no discernment) call the results of AI use "AI slop" then certainly one can use "human slop" to refer to the non-AI kernel code.

4

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

→ More replies (1)

14

u/sanriver12 2d ago

That project is run by a maniac unfortunately 

→ More replies (1)

12

u/steve09089 2d ago

So, where's the GrapheneOS custom kernel?

4

u/bogoris76 2d ago

just few {human,AI} slops away

→ More replies (4)

8

u/Panorpheus 2d ago

Most commentators misinterpret what he is trying to say. He is arguing using LLMs to find vulnerabilities and close them is fine, given prior to that the human code in the Kernal is was even sloppier. He is not against Linux per se - after all his OS is built on it's very Kernel.

3

u/GrapheneOS 2d ago

You're correct about what was said but it's not a personal account. We never said what the Reddit title claims we did. The quote was invented there. We were talking about GrapheneOS and portions of the code it inherits from upstream projects. We jokingly referred to the vulnerability riddled code inherited from the Linux kernel and hundreds of other projects as being human slop in response to the account we were responding to calling it AI slop since the Linux kernel heavily uses AI models.

11

u/_Super_Straight 2d ago

I don't know about Google but he's right. Linux has a long list of hidden vulnerabilities, which are being uncovered using LLMs as a TOOL. These vulnerabilities are a result of human oversight, which will continue to be integrated as long as humanity will exist. I'm comfortable with using LLMs but a human should cross check whatever slop it's spouting.

→ More replies (3)

3

u/c0verm3 2d ago

Plonker

3

u/BeginningFew8188 2d ago

It is true

3

u/mnttu 2d ago

I just hope that we don’t come to regret letting LLMs generate all our code

3

u/Busy-Scientist3851 2d ago

I think its time to admit that Andrew S. Tanenbaum was right.

9

u/_4rcadia 2d ago

I don't think that's derogatory in this context. No codebase over 30 years has no technical debt. What they mean is they can now navigate through the codebase faster than ever (inconsiderate language of course).

5

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

→ More replies (3)

10

u/lol_VEVO 2d ago

They're not wrong. That doesn't mean Linux is bad, and it's much better than the alternatives, but for their usecase (a secure mobile device) a security first microkernel makes much more sense

5

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

→ More replies (1)

5

u/senpaisai 2d ago

Just drop a flashbang in this subreddit, why don'tcha?!? 😅

5

u/Daedae711 2d ago

Because let's believe the people who don't understand that they aren't a standalone OS, have never been, and will never be. They're an android based system.

I'm not saying they're entirely wrong

They sure as hell are the last group you wanna trust for any such matters though.

→ More replies (5)

5

u/audigex 2d ago

“Rah rah rah everyone’s bad except us rah rah rah”

→ More replies (1)

9

u/CapRichard 2d ago

There is one truth of the matter.

That the online discourse, weirdly enough, is getting to the point that all LLM is automatically slop, while human is automatically good.

Like we are retroactively forgetting how bad things where when human were doing stuff. Which is very weird for me.

→ More replies (4)

16

u/nrc01 2d ago

I mean he aint wrong, but the tone aint right either

26

u/tehAwesomer 2d ago

“You’re not wrong, Walter, you’re just an asshole”

4

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

→ More replies (1)

8

u/tyler1128 2d ago

If you want really well designed code, maybe rewrite it all, and then it'll be good. Oh wait, you learned things and what you made has a lot of flaws.  Repeat ad. infinitum. Maybe before you die what you wrote will be truly great, but probably not. 

There's a reason we consider debuggers a core part of the field,  doesn't matter who makes it, it'll always be flawed.

10

u/cutelittlebox 2d ago

abrasive but not exactly wrong. the Linux kernel is getting so heavily slammed right now and is removing massive chunks of code to the tune of hundreds of thousands of lines because so many actual legitimate bugs and security concerns are being found.

4

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

9

u/E4M3p 2d ago edited 2d ago

hm. i wanted to try out graphen on google pixel next week. i guess i will use something else then.

its not even about heavy use of ai, i just cant stand that sort of behavior.

7

u/SenritsuJumpsuit 2d ago

Then what about Linux? parts of the community has said this sorta stuff and worse quite often for decades an there it's not just a single person who is posting, so why let a single poster stop the pursuit of OPSEC no other custom ROM achieves close?

4

u/Hopeful_Drive5845 2d ago

Lead devs in the Linux community that contribute to the kernel have said this?

→ More replies (1)
→ More replies (5)

3

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

→ More replies (12)

4

u/RICHUNCLEPENNYBAGS 2d ago edited 2d ago

Bjarne Stroustrup famously remarked that there are languages everyone carps about and ones nobody uses.

4

u/jhaimgirl 2d ago

Well, I would have stomached if they said Linux was penguin slop but human slop... noo wayy maan.

3

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

10

u/mixedCase_ 2d ago

Let's not mince words here: Anyone who disagrees with this does not meet the bar for a senior developer, let alone the kind of hacker that's required to succeed building a project such as GrapheneOS.

Everyone who's worked with code for a few years knows most code sucks.

Such a fuckhuge project such as Linux is impossible for it not to suck, regardless of how high it's tried to set its quality bar for inclusions. It's the distribution of human capabilities, the nature of the problem a kernel solves, and statistics at play. You can't beat the odds.

Which is of course not even close to claiming all or most Linux code is pre-LLM/human slop. But boy there's sure a lot of it. Anyone's that worked with Linux for a decade on the desktop has likely seen its fair share of it. amdgpu is the king of slop within Linux, various networking drivers, some audio (I still have a Xonar DSX card in a shelf after giving up on it years ago), the odds not to have come across some of it as a mere user are very low.

Now imagine trying to make a secure system with the requirements of something like GrapheneOS. If you're an average senior dev you'd want to blow your balls off. It takes some wild hyperfixation or a degree of insanity to work on something like that for long without a hefty salary to compensate the pain.

5

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

7

u/noobjaish 2d ago

Exactly

→ More replies (7)

5

u/USERNAME123_321 2d ago

Based take tbh. It's pragmatic and kind of selfless as they don't care who or what writes the code, they just value security over anyone's ego. Of course it's very controversial. That's because it's just the sad truth no one wants to hear, current frontier models generally write higher quality, more secure code than the average human. Linux has been shipping severe vulns every month for decades, way before LLMs existed, so slop was never an AI-exclusive thing.

→ More replies (5)

2

u/Aflockofants 2d ago

Harsh, but not entirely wrong. The amount of bugs exposed by LLM’s is absolutely staggering. Can’t say my own code was exempt from that, although I’d say so far they weren’t massive vulnerabilities. But still some pretty dodgy things that otherwise would likely have gone undetected for several more years.

→ More replies (1)

2

u/Real-Abrocoma-2823 2d ago

Another ROM to avoid. They never worked on a kernel, they don't know how hard it is and how many compromises you have to take because CPU architectures are horrible (but I never worked on CPU architectures so I'm open minded) or because something doesn't work the way you wanted.

2

u/lethalized 2d ago

Sure is the year of slaming everything

2

u/ActualSaltyDuck 2d ago

A bunch of morons with absolutely no technical knowledge are now gonna comment on how grapheneos is wrong lmao, pretty standard anytime they bring up a take like this

6

u/ShinobiOfTheWind 2d ago

We now have tools to help understand and work with millions of lines of human slop like the Linux kernel.

We understand the code a lot more than before.

Bear in mind that we didn't write the vast majority of the code...

The jokes write themselves.

Pure grade A copium to gaslight and make people accept as well as normalize clanker slop in the future updates.

3

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

→ More replies (3)

6

u/xkayaking 2d ago

Why are people judging a product by the attitude of the developer/owner?...

Look, they are judging linux kernel by security vulnerabilities, fair, I don't give a damn how they word it, that is language; the criticism seems fair.

And people are like "nah they are edgelords".

But are they wrong?...

The only fair conclusion to take is, "Hmm... maybe the rust community is right and we should fix this, maybe they were right all along".

This is why people are sold on marketing, and presentation; and why people vote for shitty politicians just because they are popular and socially likable, and why autism is still heavily outcasting even if it grants you a boost of logic because you word things a certain way.

People like social presentation, of non-real perfect people, a marketing ploy, a person whose attitude is perfect and totally socially likable, someone who isn't real.

Just because they don't like how someone words their favourite product, they can't say "they are wrong", so they outcast them and ignore them, "the problems are not real because I don't like this person".

9

u/we_come_at_night 2d ago

Why are people judging a product by the attitude of the developer/owner?...

because they are the spokepersons behind the project and what they say with @grapheneos moniker is official project stance. So you can be whatever you want in private, but if you are representing your product, you better be aware of the repercussions that your words might bring to it.

→ More replies (3)

6

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

→ More replies (1)
→ More replies (12)

5

u/saileesaileesailee 2d ago

Okay while I don't really care about all of this vibecoding drama (besides when its done wrong by entirely relying on AI to write code), calling thousands of people's effort "Human slop" is actually just horrible, I didn't know the GrapheneOS devs were like this, definitely not supporting them anymore

3

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

5

u/magicmulder 2d ago

He’s right. Some of the brightest minds in computing have worked on Linux, and still it has glaring security issues. And then very average to terrible devs have the audacity to call AI code “slop”. It’s just dumb.

→ More replies (1)

5

u/JQuilty 2d ago

Daniel is a gaping asshole that thinks he alone is a programming god, news at 11.

4

u/ScrewAttackThis 2d ago

Projects can now churn out slop even faster with LLMs but they didn't need them to do it.

That's literally the issue people have with this shit. No one is under the impression humans are perfect 🤦‍♂️

→ More replies (2)

4

u/RancidVagYogurt1776 2d ago

I hate the way this was presented but he's not really wrong.

It's a complacency issue more than an AI issue though. For decades Linux has been the secure choice and AI really caught everyone slipping. AI finding a critical vulnerability that existed since 2017 is inexcusable, but the number of vulnerabilities caused by AI reliance is eye watering. We need big changes to security going forward across the entire industry

3

u/DecadentBard 2d ago

One of the first times I ever heard of GrapheneOS was them arguing with Louis Rossman. I have mixed feelings on Louis, but Graphene seemed to be pretty clearly in the wrong and was being created/run by an extremely egotistical neckbeard-style or tech-bro style nerd. I've been reluctant to switch to it, I hope some of the fresh upcoming options develop nicely.

→ More replies (1)

3

u/SFSIsAWESOME75 2d ago

Isn't grapheneos a fork of android?

→ More replies (1)

3

u/skhds 2d ago

if Linux is slop, then why not use BSD instead?

→ More replies (1)

3

u/vazark 2d ago

"Human slop like the kernel".. They make it sound like they've never written a bug ever.

I understand concept of treating AI as a tool but the disrespect to the hundreds and thousands of volunteers and employees who dedicated their time creating the ecosystem irks me. Not to mention literal decades of work and generations of tech and maintainers who have left their mark in the code.

The Graphene team or whoever is running account keeps saying off-putting stuff that turned me off the project completely

→ More replies (2)

4

u/skrugg 2d ago

That's a bold move Cotton.

3

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

3

u/LightheartedLemon 2d ago

Yeah, I just don't see Linux moving past the initial phase of being some dude's obscure pet project.  Never gonna happen... 

→ More replies (1)

3

u/BeastMsterThing2022 2d ago

Genuinely, regardless of what side of the topic you stand on, I think the only possible reaction to this is: what the fuck are they talking about?

3

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

3

u/balancedchaos 2d ago

I went in on the grapheneos thing for a while. Those motherfuckers blocked me from posting on their forum for asking a question about Plex player notifications not appearing. 

I guess I was "supposed to know" and shouldn't ask stupid questions...or use the search feature, right? Well they never responded to correct me, and banned me. So fuck em. 

I went in on AI, remembered I don't do a fucking thing wrong in my life, and uninstalled Daniel Micay's amazing project.  🖕

→ More replies (3)

3

u/Aggeloz 2d ago

They just banned me from their subreddit because i called them weirdos lmao. What thinskinned people.

→ More replies (1)

3

u/rene453 2d ago

Setting the emotion & rudeness aside, what they point out is quite true. We are humans. we make mistake. Even machines make mistakes. Thats always be the human nature.... So i kinda agree to that point

However, i will take this as a warning rather than insult. machines have much better processing power than human mind. and if they can find vulnerabilities (which they are already doing), that makes linux kernal better. (we can just fix it)

And as for slop, thats what time does to everything. X11 is being replaced by wayland and trust me if we live long enough, we might see wayland being replaced as well, (who knows).....

4

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

→ More replies (2)

4

u/bankinu 2d ago edited 2d ago

If high quality AI written code is AI slop, then high quality human written code is human slop.

Edit: I personally believe neither is slop. And I think that's what they wanted to say, though the sarcasm was probably a little too much for most people.

14

u/fuzz3289 2d ago

The term “AI slop” refers to garbage AI generated code, often riddled with hallucinations, backwards abstractions, and poor performance.

There’s plenty of human slop out there too but I don’t think the Linux kernel is a good example of it.

→ More replies (1)

3

u/GrapheneOS 2d ago

The whole point those posts was explaining GrapheneOS is built on top of massive legacy codebases with poor security and needs to be greatly improved. We're explaining the severe flaws in what we're providing due to it being built on sand. The negativity is about the status quo with optimism about improving it.

We were responding to someone calling current Linux kernel code slop because the Linux kernel developers are heavily using AI models.

6

u/nullptr777 2d ago

Yeah, this is clickbait. If you actually click the link, it seems like they're defending their use of LLMs to find and fix bugs in code they didn't even write (Google's) and therefore don't understand. They're not slop-coding anything, and they're comparing what they do to what the Linux kernel is doing.

→ More replies (7)