The problem is if you lack backwards compatibility, you won't see people migrate to it. At best that means you need a big emulation layer; at worst your OS isn't different enough to be worth the switch.

The lack of vertical integration in the modern stack is surprising. We’ve spent 30 years treating the UNIX paradigm as the "end of history," while burying ourselves in layers that add zero mechanical value.

I initially thought the containerization movement of the early 2010s would be the first step toward redefining the OS—a way to finally slim things down. Instead, it just became a more efficient way to pack up the same baggage. We created a "reduction" in deployment complexity, but we haven't seen a continued effort to use those tools to actually change the paradigm.

I expected vertically integrated systems to become the norm by now—where building an executable would be an experience similar to containerization, but resulting in a lean, data-centric unikernel.

Instead, we are burning CAPEX on YAML sidecars in K8s clusters and N-tier abstractions that exist solely due to the large heterogeneity of the deployments that they never should have entered in the first place. We are spending more energy on the friction between layers than on the actual business of computation.

I was hoping for a return to sanity with the DBOS [1] research, looked like an attempt to rethink systems from first principles. But it seems that effort hasn't fully kicked off in the way the industry desperately needs.

[1]: https://dsail.csail.mit.edu/index.php/dbos/

If you haven't already, take a look at Plan 9, and maybe Rob Pikes talk "The Good, the Bad, and the Ugly: The Unix Legacy"

For the state of the art, look at seL4[0], LionsOS[1] and Genode[2].

0. https://sel4.systems/

1. https://www.lionsos.org/

2. https://genode.org/