[HN Gopher] Isolates, microVMs, and WebAssembly
       ___________________________________________________________________
        
       Isolates, microVMs, and WebAssembly
        
       Author : charliermarsh
       Score  : 29 points
       Date   : 2022-09-26 20:20 UTC (2 hours ago)
        
 (HTM) web link (notes.crmarsh.com)
 (TXT) w3m dump (notes.crmarsh.com)
        
       | rektide wrote:
       | On Micro-VM's specifically, shout out to Wyrcan[1], which is open
       | source software similar-ish to Fly.io in taking a container image
       | & booting into it. There's no platform here, but it's an advanced
       | & secure bootloader for a container images that looks like the
       | core critical capability furthest under the hood.
       | 
       | Back to isolates, I'd really love to see v8 isolates gain some
       | more whatever it takes for people to be less critical about it's
       | multitenancy. I havent really understood what the criticism is
       | but it's fairly active. Since the process has to do it's owm
       | scheduling of work, just having something like cgroups & resource
       | priority seems like a fairly obvious absense: make sure everyone
       | gets a turn. This scheduling seems semi obvious. But I think the
       | security-minded folk are paniced over a lot more, and likely with
       | legitacy, but the name isolates is afaik somewhat reasonably
       | truthful, that data is fairly secure across isolates in the same
       | process.
       | 
       | Throwing in a bonus ask, it'd be sweet if isolates could
       | migrated. Perhaps snapshotting can already maybe do this? Being
       | able to load manage is important! Even if v8 doesnt want to have
       | vast multi-tenant scheduling capabilities my trivial dumb feel is
       | that just moving aggro processes elsewhere would be a great start
       | to handle aggressive tenant sub-proceeses.
       | 
       | I wish I had links on hand, but one of the things that most
       | opened my horizons on wasm & it's role was considerations that
       | browsers should be able to have multiple instances of a module.
       | Like, if someone depends on a module, does everyone always get
       | the one singleton instance? Can the browser start creating
       | multiple instances if there's a lot of consumers? Very clear
       | browserside question that really opened the floodgates that, oh,
       | there's a lot of ways we could go forward with this!
       | 
       | [1] https://gitlab.com/wyrcan/wyrcan
        
       | pyrolistical wrote:
       | The future is here, people just haven't noticed yet
        
       ___________________________________________________________________
       (page generated 2022-09-26 23:01 UTC)