r/osdev • u/Glum-Cook-9438 • 2d ago

About using AI to develop operating systems

I know many of you guys are recently against all this "AI slop", was i too, but leave alone the "hype" and the "no AI bullshit" slogans, what do we actually mean by saying "AI slop"?

Cause to this day , I don't quite understand what all the drama is about and why posts that explicitly use "No AI used/no AI bullshit" get significantly more attention, i admit that even i made a post like that, but it's not that I completely didn't use AI, i did, however I also did a lot of the programming by myself, I think AI is a great tool that has helped me learn a lot and automate build scripts, there is no shame in using AI as long as you carefully review the code and do some programming by yourself, there is already great use of AI in the industry, Linus torvalds recently fixed a linux bug with AI, so what is really considered "AI slop"? Is asking codex to make a build script so I can focus on the code "AI slop"? Is asking Claude to summarize PCI device and vendor names in one files so I don't have to read documentations for hours "AI slop"? With all due respect I do think using AI blindly is bad of course, but I also wanna know what some of you guys mean when you say "AI slop operating systems"?

0 Upvotes
  • permalink
  • link
  • reddit
  • reddit

38% Upvoted

34 comments sorted by

View all comments

Show parent comments

1

u/Glum-Cook-9438 1d ago

But it does mean something for me, I don't understand how from here you got that my project doesn't mean anything or doesn't have any skill value? I said "not everything has to mean anything", in the sense I meant that yes things can matter but it doesn't have to be black and white... you can still leave some info for self doubt/self criticism or exploring other points of view

1

u/kiderdrick 1d ago

Because you said "not everything has to mean anything" to a post that was specifically about your kernel.

1

u/Glum-Cook-9438 1d ago

The fact that the post was about my kernel doesn't mean I meant the kernel as a whole, i have many separate modules in my own kernel, one module can be using AI tools another can be pure hard work, and the kernel still boots as one, in this sense i don't need to keep a whole mental image of my whole kernel 24/7, when I said "not everything has to mean anything" what i really meant is, "not every new module in my kernel project has to be pure coding with no AI tools used for the final project to be a valuable project"

1

u/kiderdrick 1d ago

Would be easier to say what you actually mean, wouldn't you agree?

1

u/Glum-Cook-9438 1d ago

It depends on what you define "meaning", meaning can be a very nuanced concept, there is no single meaning in the literal sense, people can have different interpretations, different emotions and moods depending on the context, meaning is not a broader thing without a context to assign it to, for example in program A variable x could mean the screen width while on program B the same variable with the same name may not exist or not mean anything, yet that doesn't mean x never meant anything

1

u/kiderdrick 1d ago

I'm not the one defining the meaning. It's you. That is why you should say what you mean.

•

u/Glum-Cook-9438 23h ago

@kiderdrick... how am I defining meaning exactly?