News for hackers. Stuff that matters.
Re:WebAssembly: The New Kubernetes? by samwillis on Friday January 21, 2022 @04:48AM (#30021330)
I’m a Django developer at hart and have been for 15 years. The dream I have that I hope WASM will provide is to package any app (Python, Ruby, Rust, Go, anything!) up into a single binary file that we can deploy anywhere, on any architecture (x86, arm). No more packaging nightmare, no more containers, just a single file that runs anywhere. Maybe it’s wishful thinking but I hope it happens.
Re:WebAssembly: The New Kubernetes? by 1337shadow on Friday January 21, 2022 @05:41AM (#30021750)
It's PyInstaller: https://pyinstaller.readthedocs.io/en/stable/

Or containers.

Re:WebAssembly: The New Kubernetes? by joconde on Friday January 21, 2022 @01:16PM (#30027592)
PyInstaller is hackish though, I had to add tricks to setup.py by trial-and-error until I found why some config file or sub-module of a sub-package wasn't included when everything else was. It's also slow to launch, because it extracts the code into a temporary directory before importing python.dll, which then imports all the rest.

Containers are fine for a server after installing the runtime, which is already one too many steps. There isn't a self-contained app format that can run without installing something else before starting it.

Re:WebAssembly: The New Kubernetes? by manmal on Friday January 21, 2022 @08:09AM (#30022944)
Containers are not architecture-agnostic. In theory they are not even kernel version agnostic, though Docker seems to work around that.
Re:WebAssembly: The New Kubernetes? by dilyevsky on Friday January 21, 2022 @01:06PM (#30027432)
“Containers” are basically Linux only and that means they can freeride off Linux’s really stable userland api
Re:WebAssembly: The New Kubernetes? by rich_sasha on Friday January 21, 2022 @05:31AM (#30021679)
Isn’t this basically JVM?

Jython is a thing.

Re:WebAssembly: The New Kubernetes? by samwillis on Friday January 21, 2022 @06:01AM (#30021907)
The parallels between WASM and the JVM are well known. But I like to think of it as WASM is building upon the knowledge gained from the JVM.

With the JVM you had to reimplement your language to target it, or design a new one. WASM was planned from the start to be a target for existing compiler frameworks such as LLVM and GCC.

With Jython you could not use extensions that were designed for CPython. With WASM you can. Take a look at Pyodide, they have ported most of the scientific Python stack to WASM, that’s not possible with Jython.

https://github.com/pyodide/pyodide

Re:WebAssembly: The New Kubernetes? by pjmlp on Friday January 21, 2022 @10:23AM (#30024730)
Just like IBM TIMI, TenDra, Amsterdam Compiler Toolkit, CLI.

That is the thing with WebAssembly marketing, not being aware of bytecode formats history.

Re:WebAssembly: The New Kubernetes? by immibis on Friday January 21, 2022 @02:03PM (#30028366)
And yet WASM still has warts that make it impossible to simply transpile existing binary code onto it.

Java, by the way, also isn't stopping you from storing all your data in one big ByteBuffer, which is how WASM handles memory.

Re:WebAssembly: The New Kubernetes? by pjc50 on Friday January 21, 2022 @06:21AM (#30022031)
Sort of - and the JVM has been a thing on webservers since WebSphere and Tomcat. But never quite achieved the ease of use. I'm not aware of a service you can just chuck a jar at and your webservice spins up on your (sub) domain?

Jython has been a casualty of the 2 => 3 transition.