News for hackers. Stuff that matters.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by jey on Tuesday May 30, 2023 @11:51AM (#36126292)
Sounds and looks like it was fun to implement, but is there a motivating use case? Or is it more for technical/hacking interest?
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by garganzol on Tuesday May 30, 2023 @12:06PM (#36126510)
I think this may become the basis of an operating environment where you do not have to concentrate on "how to run" something. Instead, you get straight to the job of deciding "what to run" so you can reap the benefits in no time without all the devops and SaaS drama.

The closest contemporary thing is fly.io, but recently they became less strategic and more opinionated. Another attempt is sandstorm.io but it was abandoned by the original authors. So... maybe WASM and the initiatives like WASIX will give it to us?

Re:WASIX, the Superset of WASI Supporting Threads, Processes... by rapnie on Tuesday May 30, 2023 @12:17PM (#36126666)
Looks like Sandstorm still has the original founders on the FOSS project they now are, just not as a company. Both co-founders working for Cloudflare now:

https://sandstorm.io/about

Re:WASIX, the Superset of WASI Supporting Threads, Processes... by paulgb on Tuesday May 30, 2023 @02:06PM (#36128277)
Ideas from Sandstorm also live on in Cloudflare's Durable Objects:

> We don't have any current plans, but... I was the co-founder of Sandstorm.io before going to Cloudflare, and Durable Objects are very much inspired by parts of Sandstorm's design. So yeah, I've absolutely thought about it. ;)

https://news.ycombinator.com/item?id=24619148

Re:WASIX, the Superset of WASI Supporting Threads, Processes... by ocdtrekkie on Tuesday May 30, 2023 @04:47PM (#36130534)
The about page is very not updated, FWIW. I started a PR and then did not finish it. About every other week someone looks at it and gleans incorrect insight from it, so I really should finish that PR...

Most contributions presently come from outside the original Sandstorm team, but some significant features and refactors have come out since the company shut down from former employees too.

Re:WASIX, the Superset of WASI Supporting Threads, Processes... by dboreham on Tuesday May 30, 2023 @12:06PM (#36126521)
If only someone had built this 25 years ago...
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.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by xet7 on Tuesday May 30, 2023 @04:01PM (#36129891)
> Another attempt is sandstorm.io but it was abandoned by the original authors.

Sandstorm is still maintained:

https://github.com/sandstorm-io/sandstorm

https://sandstorm.io

At Libera.Chat IRC #sandstorm . Welcome :)

Re:WASIX, the Superset of WASI Supporting Threads, Processes... by sitkack on Tuesday May 30, 2023 @04:18PM (#36130138)
Sandstorm is now Cloudflare.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by kentonv on Tuesday May 30, 2023 @04:40PM (#36130447)
No, Sandstorm is not owned by Cloudflare. Cloudflare hired most of the team (myself included) but the company remained independent. Sandstorm the company dissolved last year. The open source project remains alive via the Sandstorm Community on Open Collective[0], but admittedly there has been little activity lately.

[0] https://opencollective.com/sandstormcommunity

Re:WASIX, the Superset of WASI Supporting Threads, Processes... by sitkack on Tuesday May 30, 2023 @04:45PM (#36130511)
Sorry, I was being obtuse in that. CF now employs enough people that think "Standstorm" that it will eventually and perhaps does now support all the machinery necessary to implement Standstorm on CF.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by kentonv on Wednesday May 31, 2023 @09:08AM (#36137936)
Ah! Fair point. ;)
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by ocdtrekkie on Tuesday May 30, 2023 @04:40PM (#36130448)
Cloudflare hired most of the Sandstorm startup team. It did not acquire Sandstorm, and it remains an independent open source project.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by predictabl3 on Tuesday May 30, 2023 @05:01PM (#36130745)
As a long-time Nix-er, who was into Docker before anyone know what it was, and was committing to Kube pre-1.0, I just kinda giggle. It's all just shuffling puzzle pieces around. Whether you're compiling your Rust to x86_64-linux and shoving it in a container, or compiling it to WASI and shoving it in some runtime... there's still gonna be some horrifying bash script orchestrating it. Because there always is.

There's still going to be someone running Kubernetes, or provisioning VMs.

> where you do not have to concentrate on "how to run" something.

Sounds nice, been hearing this pitch for a long, long time. I really don't mean to be harsh, but it just sounds naive at this point.

Re:WASIX, the Superset of WASI Supporting Threads, Processes... by paulgb on Tuesday May 30, 2023 @02:11PM (#36128340)
There are a lot of people betting on WASM as a successor to linux containers for many use cases. Sockets and threads have been the main barriers IMHO to that happening.

One exciting advantage of WASM over containers is that it can run across different processor architectures and operating systems (the proprietary distribution of Docker runs on Mac but it does so by running a linux VM and containers not built for amd64 are noticeably slower).

Re:WASIX, the Superset of WASI Supporting Threads, Processes... by pjmlp on Tuesday May 30, 2023 @03:28PM (#36129403)
Reinventing Java and .NET application servers...
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by tokera on Wednesday May 31, 2023 @01:14AM (#36134708)
Yes indeed, a much improved JVM or .NET runtime - those shoes will be hard to fill given how great Java and .NET has been for the enterprise world but hey lets give it a shot... exciting times!