https://hackerpaper.kaipfister.de/p/2506.03876/Collected HN comments and submissions linking this paper.enMon, 02 Nov 2026 11:16:22 GMThttps://news.ycombinator.com/item?id=44402000urn:hackerpapers:mention:2506.03876:44402000Sat, 28 Jun 2025 02:43:17 GMT<p>There are projects that make more sense: https://arxiv.org/abs/2506.03876 https://github.com/asterinas/asterinas The reasons we encounter pattern issues forcing Linux into a polyglot is not a new phenomena: https://en.wikipedia.org/wiki/Second-system_effect Best regards =3</p><p><a href="https://hackerpaper.kaipfister.de/p/2506.03876/">Paper and discussion history</a>. A mention is not an endorsement.</p>cs.OShttps://news.ycombinator.com/item?id=44325381urn:hackerpapers:mention:2506.03876:44325381Fri, 20 Jun 2025 07:07:34 GMT<p>I had the same reaction that this sounded all very backwards, but reading the introduction in the paper[1] made it more clear: The kernel is logically divided into two parts: the privileged OS framework (akin to a microkernel) and the de-privileged OS services. Only the privileged framework is allowed to use unsafe, while the de-privileged services must be written in safe Rust completely. As the TCB, the privileged framework encapsulates all low-level, hardware-oriented unsafe operations behind safe APIs. Using these safe APIs, the de-privileged OS services can implement all kinds of OS…</p><p><a href="https://hackerpaper.kaipfister.de/p/2506.03876/">Paper and discussion history</a>. A mention is not an endorsement.</p>cs.OS