News for hackers. Stuff that matters.
Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by nine_k on Wednesday June 21, 2023 @03:13AM (#36415378)
Plan 9 had many improvements over Unix of its times. It opened up too late to conquer the world though. Some good things from it were imported into Solaris and Linux later.

Technological progress likes to reinvent itself, looping back to the same idea that did not work last time, and maybe making it a hit finally. Two examples:

- Apple Newton, 1992 (a flop) -> Palm Pilot, 1997 (niche success) -> Apple iPhone, 2007 (world domination).

- Java Virtual Machine, 1994 (server-side world domination, a flop in the browser) -> Inferno OS, from the makers of Unix and Plan9, 1996 (a flop) -> WASM (prospects of world domination in the browser).

Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by torginus on Wednesday June 21, 2023 @03:28AM (#36415492)
I personally don't like WASM. I think the Native Client (which is more than a decade old today) was a much better technical solution. It used actual cpu native assembly bundled with a verifier, and had actual good integration into low-level platform APIs like graphics, threading, etc. instead of using this weird Javascript bridge approach. Due to it being native code from the start, it also had none of the startup performance issues, that plague WebAssembly.

WASI also seems like a wrong approach, considering it inherits the limitations of WASM, like problems with memory, allocation and multithreading and hacks needed to overcome them.

VM-s are also kind of a wash for me too, since nowadays the most popular way to run software in a portable/sandboxed manner is Docker, which is NOT cpu-agnostic, even if you ran a JVM app in it, the bundled JVM would be CPU arch dependent.

Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by nine_k on Wednesday June 21, 2023 @09:15AM (#36418046)
Actual CPU native assembly? It would need to support x86, x64, and aarch64 by now. (And likely RISC-5 in the near future.)

The point of VMs like WASM is not (specifically) performance though, even if performance is desirable. It's the minimal, fixed standard, and the isolation.

If you badly need native performance, develop a native application %)

Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by vilunov on Wednesday June 21, 2023 @12:59PM (#36421169)
Or it could get translated to the target ISA by the user-agent Rosetta-style, suffering the same warmup issues, but only on some architectures.
Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by torginus on Thursday June 22, 2023 @04:34PM (#36438544)
Yeah, actual native assembly. I think doing a cross compilation for 2 architectures (x64 and aarch64) is more than doable, even 4, if you want to be thorough.

> The point of VMs like WASM is not (specifically) performance though

I feel like it is though. There was another thing, called asm.js back then, which was a subset of javascript that was easily translatable to machine code. It was a giant hack, and performed worse than NaCl.

I feel like WASM is more of a spiritual successor of that thing.

> If you badly need native performance, develop a native application

And pass up the ease of distribution/compatibility browsers offer?

Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by anthk on Wednesday June 21, 2023 @05:11AM (#36416214)
> world domination

No. Android won. The concept from iPhone won, but Android it's the world leader.

Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by nine_k on Wednesday June 21, 2023 @09:20AM (#36418091)
Yes, I mean the concept, the approach.

Unix as a concept (a set of ideas and interfaces) achieved world domination, but it's not the original AT&T kernel, and not the original AT&T userland.

Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by regentbowerbird on Wednesday June 21, 2023 @06:34AM (#36416795)
When you say Inferno led to WASM, is it just conceptual or is there a concrete link?
Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by lproven on Wednesday June 21, 2023 @08:08AM (#36417427)
It's not even conceptual.

It's an entirely separate, kludgy and vastly inelegant, reinvention of a concept that had already been done much better.

First in Tao Group's Taos, later much refined and improved in Elate and Intent.

Then done in a more Unixy way in Inferno.

Inferno embeds the cross-platform runtime VM right into the kernel and makes it the default.

WASM bodges a cross-platform runtime VM together out of chunks of web browser and Javascript tech, and then others rip it out of the browser and make it run standalone.

Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by garaetjjte on Wednesday June 21, 2023 @09:29AM (#36418195)
There is basically none Javascript tech in WASM.
Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by lproven on Wednesday June 21, 2023 @10:30AM (#36418910)
As I understand it, and I could be wrong, the origins of the project lay in trying to target the output from a compiler to a bytecode like intermediate language that the JavaScript runtime could execute. I am more than happy to believe that no trace of that is left now, but I think that is more or less how it got started.
Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces by nine_k on Wednesday June 21, 2023 @09:22AM (#36418116)
Inferno did not "lead" to WASM. Palm Pilot did not "lead" to iPhone.

Instead I'm trying to show the same general idea tried over and over, at different times and from different angles. The arrows just show the sequence in time.