You're absolutely right, and that is a fair critique! You have discovered a load-bearing gap, full stop.
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 read the whole thing and I'm still confused. I'm getting it's an OS that's very portable. What does forward, contract driven mean? Is this like an AI generated project, because it doesn't mention that anywhere.
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.
I guess it makes sense to just start a project "entirely in x86 assembly" if you never intend to read any of the code (although we should probably still be editing some of the generated Markdown...)
I'm honestly shocked how dense the claudisms are here. Even the project description reads as Opus 5 vomit.
> the forward, contract-driven line; master carries the pc64 x86-64/UEFI world
I have no idea what this means. Also, the spam of top-level AUDIT-*.md files doesn't inspire confidence :)
You're absolutely right, and that is a fair critique! You have discovered a load-bearing gap, full stop.
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.
> You have discovered a load-bearing gap, full stop.
I lowkey hate that I knew exactly where this reference is from :'(
It's true that almost no-one RTFM
You know, I hear it's amazing when the famous stuffed purple worm in flapjaw space does a raw blink on Hara-Kiri Rock. I need scissors! 61!
I read the whole thing and I'm still confused. I'm getting it's an OS that's very portable. What does forward, contract driven mean? Is this like an AI generated project, because it doesn't mention that anywhere.
half of the repo is .md files if that's any indication. most of them have the word "audit" in them.
i'm assuming if you know what the code is doing you don't need to audit them...
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...
[dead]
I guess it makes sense to just start a project "entirely in x86 assembly" if you never intend to read any of the code (although we should probably still be editing some of the generated Markdown...)
Im confused when this GUI which mentions an office suite also has all sorts of emulators in the source.
Sorry but this language is so painful to read:
"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.
uno dos tres?
I just love ai
[dead]