I think the problems with this article are well covered already. Just a suggestion for Joyent: articles like this are damaging to your excellent reputation, would suggest a thin layer of review before hitting the post button!<p>Some additional meat:<p>- The complaint about Mirage being written in OCaml is nonsense, it&#x27;s trivial to create bindings to other languages, and in 40 years this never stopped us interfacing our e.g. Python with C.<p>- A highly expressive type&#x2F;memory safe language is not &quot;security through obscurity&quot;, an SSL stack written in such a language is infinitely less likely to suffer from some of the worst kinds of bugs in recent memory (Heartbleed comes to mind)<p>- Removing layers of junk is already a great idea, whether or not MirageOS or Rump represent good attempts at that. It&#x27;s worth remembering that SMM, EFI and microcode still exist on every motherboard, using some battle-tested middleware like Linux doesn&#x27;t get you away from this.<p>- Can&#x27;t comment on the vague performance counterarguments in general, but reducing accept() from a microseconds affair to a function call is a difficult benefit to refute in modern networking software.