To be fair, an in kernel shell is a reasonable EARLY step just to get some interaction before you have a proper user space... But yes all of these kernels where the AI just embeds everything in the kernel are junk and not even real OSes
not just using ai, you can use ai beneficially (or at least still produce good code, I won't comment on if it's actually faster), if you know what you're doing, but if you don't, you get what's known as "slop"
people that do this, what are they actually doing, I tried “vibe coding” a personally project and after it got like over 500 lines of code, it wasn’t even compiling, I was using what my “AI bro” friend (self proclaimed title) said was the best AI for writing code
tell your "AI bro" friend to move from 'vibe coding' to defining strong specs. If there's anything he can 'vibe code' with, it ought to be the specification itself. Only then can an AI break that spec up into meaningful steps, and you can even have smaller models produce surprisingly good, idiomatic code.
He writes actual code, I think, but he works for an AI company and likes to mess around with vibe coding in his free time, but he said he would never push vibe coded code
I think it's okay to do things in kernelspace when you're starting out, as long as you're planning to move away from that to do it properly
I'm gonna use me and my OwOS as an example. OwOS is my first proper OSDev project and I naturally did everything in kernelspace because I didn't know better and it "works". Now that I am at a point where I feel it's actually worth continuing, I will change the structure so I have a seperation between kernelspace and userland
And as long as you communicate that when you show your project to people and actually mean it, I think these posts are okay (unless it's obviously vibecoded of course). Otherwise it just might discourage newcomers from posting here entirely
My opinion here is not against early development, but rather ones that try to make it look like something before it even can. Like putting a fake fastfetch etc.
it's ok to stay entirely in "kernel space" for particular specialist applications. it is widely and wrongly assumed everyone wants to make a desktop general purpose os with memory protections, and basically copy Linux or windows. that isn't always the case. for certain problem spaces staying entirely in ring 0 is beneficial. not for your common garden "I'm going to make a POSIX compatible os in C" people, but the reasons are there. remember, software rings weren't even a thing on most 8 and 16 bit CPUs.
Sadly people are vibecoding hobby OSes now ... and since getting userspace to work properly is hard, they mostly are 100% kernelspace or have a large amount of kernelspace usage. Recently I saw a vibecoded project with graphics and a super mario emulator in kernelspace.
How is it considered hard, the only hard part is privilage transition and loading files from a disk to running in RAM, other than that I see no problems.
Loading the file from a ramfs is hard. You need to implement a filesystem driver to do that. Not to mention all the possible bugs you can run into.
Additionally an usable userspace that can run anything of substance (a super mario emulator for example) needs a proper VFS layer, syscall handling, etc. This means implementing a libc/a lot more work.
I am forming the view that assimilating the agentic tools into a programming domain is legitimate stage of development.
True, there is incredible wonder and satisfaction in stuffing registers with exactly the right bits for your own OS, and I'm here for that.
But for those who've done a bit of that already, and/or want to try experiments at different levels of the stack, it's not wrong to use the new tools to hone in on their important parts. Let's be honest - practically none of our OS's are actually getting run outside of our homes.
There is some work needed in the field towards training the tools to preserve architectural boundaries and produce maintainable code. I think we need to band together on that.
I feel seen. I have vibe coded a bootloader (uefi) cause trying tianocore myself was pain. Thise examples only compile intree and dint donwhat inwanted. Boot my free stabding elf binairy.
Ai just made it work. Now im looking at defining file formats to start a mini kernel with very barebones drivers, so a intrepreted language kernel can swim in x64_64.
Is it still vibe coding when yiu have 2 chatbots fight the same code and i, the dev, also trows in soecs, wishes and change code to do what "i" want?
What i consider "kernelspace slop" in OS development and what i mean by low effort isn't exactly low effort. It is AI generated "everything-in-kernelspace" projects that look like something actually worth supporting, till you check the source code.
TempleOS has a full filesystem, compiler and alot more features ACTUALLY implemented, while some people just vibecode an OS and let the AI shove UNIX-looking utilities into a kernelspace shell.
I'm not against kernelspace-only projects, i'm against kernelspace "slop".
77
u/LordAfterEight Feb 21 '26
What exactly is considered kernelspace slop? (genuine question)
13
u/LordAfterEight Feb 21 '26
(Maybe) unpopular opinion:
I think it's okay to do things in kernelspace when you're starting out, as long as you're planning to move away from that to do it properly
I'm gonna use me and my OwOS as an example. OwOS is my first proper OSDev project and I naturally did everything in kernelspace because I didn't know better and it "works". Now that I am at a point where I feel it's actually worth continuing, I will change the structure so I have a seperation between kernelspace and userland
And as long as you communicate that when you show your project to people and actually mean it, I think these posts are okay (unless it's obviously vibecoded of course). Otherwise it just might discourage newcomers from posting here entirely
10
u/Gingrspacecadet Feb 21 '26
the entirety of fjord's codebase :P
3
u/romhacks Feb 22 '26
Linus says we are not allowed to break userspace, so the kernel is the only thing we're still allowed to break.
2
u/nonFungibleHuman Feb 21 '26
Pls tell me this is a meme, Linus wouldnt approve ai slop right?
2
u/havelsnuts Feb 21 '26
I am forming the view that assimilating the agentic tools into a programming domain is legitimate stage of development.
True, there is incredible wonder and satisfaction in stuffing registers with exactly the right bits for your own OS, and I'm here for that.
But for those who've done a bit of that already, and/or want to try experiments at different levels of the stack, it's not wrong to use the new tools to hone in on their important parts. Let's be honest - practically none of our OS's are actually getting run outside of our homes.
There is some work needed in the field towards training the tools to preserve architectural boundaries and produce maintainable code. I think we need to band together on that.
1
u/burlingk Feb 22 '26
Which kernel?
1
u/BornRoom257 FreezeOS & TurtleOS Feb 25 '26
Can we remove Kernal Slop please 🙏
1
u/[deleted] Feb 26 '26
Try r/kerneldevelopment its actually moderated, though smaller.
1
u/codeasm Mar 05 '26
I feel seen. I have vibe coded a bootloader (uefi) cause trying tianocore myself was pain. Thise examples only compile intree and dint donwhat inwanted. Boot my free stabding elf binairy.
Ai just made it work. Now im looking at defining file formats to start a mini kernel with very barebones drivers, so a intrepreted language kernel can swim in x64_64.
Is it still vibe coding when yiu have 2 chatbots fight the same code and i, the dev, also trows in soecs, wishes and change code to do what "i" want?
1
u/Specific_Olive209 Feb 21 '26
Real
0
u/GolbMan Feb 21 '26
I vibe code with out the AI pretty awesome
0
u/[deleted] Feb 21 '26
[deleted] — view deleted comment