Very cool! Mad props friend

The project was made with an older version of Zig, which used strings as keys in zig.build.zon before but then it was changed to use enum literals in 0.14.0 IIRC.

Bizarre that the README.md does not specify that this is for RISC-V.

I also went to look to see where "console output" was implemented, and ... it looks like it's just not? ConsoleWriter.write() calls kernel.putChar, which does not exist...

Cool projects!

A few suggestions:

- You're committing .zig-cache to git, but that's build output, so it shouldn't be under version control. You should add it to .gitignore (you already have zig-cache without leading dot).

- Your README.md refers to a CONTRIBUTING.md that doesn't exist

- It's helpful to say exactly which Zig compiler you need. It currently says "0.10.0 or later" but 0.10.0 is almost three years old now.[0] Most 0.10.0 code does not compile in 0.15.1.

[0] https://ziglang.org/download/#release-0.10.0

Sweet!

Folks interested in this may also like "Operating System in 1,000 Lines" https://operating-system-in-1000-lines.vercel.app/en/

and the implementation in C https://github.com/nuta/operating-system-in-1000-lines

I was hoping to get some commentary about the project and what lessons you learned from it. You wrote an OS in 1000 lines of Zig, but... So what? What should I take away from this? Are you posting this to encourage people to use the OS, or learn from the project? How was Zig helpful or a hindrance for this? Why limit to 1000 lines? Why did you post this?