News for hackers. Stuff that matters.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by FooBarWidget on Tuesday May 30, 2023 @01:22PM (#36127644)
By comparing to fly and sandstorm it sounds more like you're looking to solve the application hosting problem. How is that a problem solved by wasm? It's just a bytecode format and runtime, it doesn't deploy servers and load balancers. The only thing I can think of is that users build wasm binaries/containers and don't care whether the hoster uses x86 or ARM or RISC-V.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by garganzol on Tuesday May 30, 2023 @01:39PM (#36127883)
Exactly what you said, plus one more important opportunity (for the distant future): by being architecture-agnostic, the images of running WASM processes can freely travel between the nodes of a cluster, thus providing remote "fork" and roll-over capabilities. This can transform the way we create distributed software; instead of remote APIs, "queues", "buses" and "workers" we will be able to use the very same primitives we already use for in-proc and inter-proc coordination. So, the whole service like YouTube with transcoders and everything can literally be represented by just one or several executable files in a folder.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by KRAKRISMOTT on Tuesday May 30, 2023 @01:40PM (#36127898)
The biggest issue for cloud hosting/self hosting is sandboxing arbitrary hostile code. This almost always require expensive KVM-based hardware accelerated virtual machines. AWS firecracker is the same shit as hardware accelerated VirtualBox, just heavily stripped down to allow for rapid booting. WASM comes from the CloudFlare functions/V8 ideology where a language environment is sufficiently locked down, such that you don't need heavy operating system level virtualization.