LisPi<p><span class="h-card" translate="no"><a href="https://queer.hacktivis.me/users/lanodan" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lanodan</span></a></span> <span class="h-card" translate="no"><a href="https://octodon.social/@cwebber" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cwebber</span></a></span> Did you know that <a href="https://mastodon.top/tags/OpenGenera" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenGenera</span></a> had a <a href="https://mastodon.top/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>C</span></a> and an <a href="https://mastodon.top/tags/Ada" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ada</span></a> compiler (among others)?</p><p>You don't need to rewrite the drivers, you can just implement a shim (with error handling) so they can run on top of the system in their little isolated bubble like the <a href="https://mastodon.top/tags/rumpkernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rumpkernel</span></a> idea was about.</p><p>You do need those bits in some specific areas, but you can tightly constrain access to them to very specific modules & threads.</p><p>Erlang's message-passing approach isn't required for condition handling.</p>