Radical_Dreamers_ReveD'Ordinateur_OC_ReMix.mp3

Notices where this attachment appears

1. Embed this notice
   pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Friday, 29-Dec-2023 02:03:13 JST pistolero :thispersondoesnotexist:

   in reply to
   @Moon @BrodieOnLinux @Maholmire @SrEstegosaurio @dcc @dushman @mima @nerdeiro @pwm
   
   > this is an implementation detail
   
   It looks like this paper went for the obvious approach, but when I said I expect a lot of unikernels, I meant like a Forth system is a unikernel. I mean compute-dust. GreenArrays 144-core chips look like the start of a near-inevitability. (Feel free to believe it when you see it.)
   
   In more practical terms that apply today, unikernels where the application code is written in a bytecode VM have a different security model than "just write it in C and link that code in". You can do compile-time guarantees that prevent you even requiring an MMU. So you tack a blob on. You can do this kind of thing with BEAM or Inferno right now (compile some Limbo code, include only as much as needed to run that code in the builtin filesystem, boot that kernel), and I imagine people have built similar systems around more conventional kernels.
   
   > but it appears that vendors are incompetent.
   
   Many such cases. Sad!
   Radical_Dreamers_ReveD'Ordinateur_OC_ReMix.mp3