Writing an "operating system"?

What if I wrote my next C# app as if I were writing an operating system? Travel those same paths of bootloader, kernel initialization, init, userland. Why put yourself through the hassle? Operating system development has always fascinated me. I took a class on it in college, which sadly turned into a semester of incredibly boring lectures on the theory behind multi-tasking. I've tried writing little x86 bootloaders before; the farthest I ever got was while following along on nanobyte's channel: https://www.youtube.com/@nanobyte-dev https://github.com/treytomes/cocos A problem you run into quickly is writing device drivers for all of those little things we take for granted: hard drives, speakers, microphones, keyboard, mouse, etc etc etc. But it can be fun. The Familiar Boot Sequence Hidden in Plain Sight There are a series of things that happen every time a C# app that I write starts: Parse command‑line arguments Configure logging Wire up dependency injection Start hosted services Hand