UnoDOS
github.com
github.com
I have no idea what this means. Also, the spam of top-level AUDIT-*.md files doesn't inspire confidence :)
In all seriousness, many people here, including myself, regularly receive 5 to 10 page long AI generated "documentation" where it is clear the "author" never made it past the first paragraph.
I lowkey hate that I knew exactly where this reference is from :'(
It's true that almost no-one RTFM
i'm assuming if you know what the code is doing you don't need to audit them...
Right, who among us hasn't hand-written and shipped a twenty-two machines family of legacy operating systems atop a bespoke hypervisor you could explain from the top of your head.
This project looks like a labor of love and its quite cool. Haters gonna hate, but if you actually go read the Markdown there's been a lot of elbow grease put in making this work: https://github.com/hmofet/unodos/blob/master/pc64/FIX-PLAN.m...
Edit: im fairly confident we're the first humans to lay eyes on that document
"i'm assuming if you know what the code is doing you don't need to audit them..." I frankly disagree. Really depends on how you define "what the code does". If you need to know what a particular function will result in when you put an input into it, sure, yeah, you need to know how that code works. But if a function is one in a hundred thousand of other functions that all work together to do "something", it matters less how that function is implemented. What the code "does" here is provide a platform to run whatever applications you could want. A music player. A web browser. A game.
An OS is an incredibly complicated system. I don't think anyone who is part of writing one these days knows what every line of code does, nor do they really need to be able to pick a random line and understand it. So what is the use of good code style and good documentation if nobody will read will ever be expected to pick a random line, read the documentation about what it does, and understand it? Made sense when code bases were relatively small, and humans were the only entities that could read code. Doesn't make as much sense now when an LLM can read an entire OS's hundreds of thousands of lines of code in mere seconds, and understand it almost instananeously.
All I care is that this operating system I designed all by myself is functionally equivalent at the minimum to Windows 95, which at least 1000 people working together wrote.
I don't care what the code does, and 99% of my repo is not meant for humans to read, it's meant for other LLM agents to read. That's why it's largely MD files, in a language only other LLMs can understand. What is meant for humans to read is here: https://unodos.arinbakht.com/manual/ How do you open a DOC file? How do I play an MP3? How do I browse the web? Those are the parts of an OS humans actually care about, and those are explained more plainly in the user manual. How does the bootloader hand over control to the kernel? Frankly, not that important.
"What has actually been verified is a separate question from what builds, and PLATFORMS.md is the ledger that answers it:"
...that there is no way I'm going to try unodos.
https://en.wikipedia.org/wiki/Frozen_Peas
https://www.youtube.com/watch?v=V14PfDDwxlE
Back in the Agile era the most applicable one was "I gave twenty times more for you than for any other commercial I've done. You are such PESTS! Now what is it you want? In your... depths of your ignorance, what is it you want?"
But in the AI era, the most applicable quote becomes: "It's full of, of, of things that are only correct because they're grammatical, but it's tough on the ear, you see..."
If you still believe that writing software "by hand" isn't cooked, you haven't been paying attention.
We got a byte-identical seam though