News for hackers. Stuff that matters.
Re:WebAssembly: The New Kubernetes? by FreeHugs on Friday January 21, 2022 @04:18AM (#30021089)
So be it!

Until XyZ is the new WebAssembly and @!# is the new XyZ!

As long as my Django backend works and browsers support my HTML/CSS/JS frontend, I am fine.

I have the same LAMP (Linux, Apache, MariaDB, Python) SAAS project running for decades now, paying all my bills, letting me live a free life.

As long as nobody touches that, you can do all you want. Invent new fancy stacks every other year, make courses for it, migrations to it, a religion of it - I don't mind.

Re:WebAssembly: The New Kubernetes? by stavros on Friday January 21, 2022 @04:35AM (#30021218)
Having been wrangling with a monster Nuxt.js front-end that takes 30 minutes to compile for what is essentially a few pages of an eshop, I long for it to be reimplemented in Django.

SPAs are good for some things, but those things are much fewer than what we use them for.

Re:WebAssembly: The New Kubernetes? by jack_riminton on Friday January 21, 2022 @05:48AM (#30021799)
I really hope this use of SPAs for CRUD apps like eshops is going to end soon, it's completely unhinged. There's a reason why Shopify went with Rails
Re:WebAssembly: The New Kubernetes? by chrisweekly on Friday January 21, 2022 @08:33AM (#30023218)
Agreed -- but going back to Rails isn't the answer. Remix.run is moving things forward in the right way, ie PHP/Rails -> SPA -> NextJS -> Remix.
Re:WebAssembly: The New Kubernetes? by slingnow on Friday January 21, 2022 @10:33AM (#30024895)
Wow, that sounds like such a simple process! It's definitely the "right way"!

Never look back at working tech folks. That's today's lesson. If it works, don't just fix it -- remake it, rebrand it, and overcomplicate it!

Re:WebAssembly: The New Kubernetes? by chrisweekly on Monday January 24, 2022 @08:05AM (#30057088)
If you spent 3 minutes reading https://remix.run you might realize that mean-spirited sarcasm and a lazy, ignorant trope were not your best response.
Re:WebAssembly: The New Kubernetes? by jack_riminton on Friday January 21, 2022 @09:09AM (#30023659)
It sure does sound like the latest "next best thing"!

I'll stick to Rails though thanks :)

Re:WebAssembly: The New Kubernetes? by pjmlp on Friday January 21, 2022 @05:00AM (#30021427)
Same here, it is kind of funny to see Java and .NET being re-invented by haters all the time.

First they do containers to replicate application servers, and now WASM to replicate bytecode server side.

Re:WebAssembly: The New Kubernetes? by tormeh on Saturday January 22, 2022 @06:56PM (#30042134)
The JVM is actually good, but it is a bit too Java-centric. A VM without GC and with a more economic memory model is needed, and it looks like wasm is that.
Re:WebAssembly: The New Kubernetes? by ptrwis on Friday January 21, 2022 @08:32AM (#30023211)
And were these application servers (like JavaEE) that bad? Separately deployed EJB modules can also be considered microservices, and everything was much easier to manage.
Re:WebAssembly: The New Kubernetes? by pjmlp on Friday January 21, 2022 @08:48AM (#30023395)
Not at all, I am still working with modern versions of them.

In fact I consider Kubernetes much worse experience, regardless of how much hate Websphere and Co might get.

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.

Re:WebAssembly: The New Kubernetes? by aenario on Friday January 21, 2022 @04:44AM (#30021291)
I think your LAMP (Linux, Apache, MariaDB, Python) is a fancy new LAMP (Linux, Apache, MySQL, PHP).
Re:WebAssembly: The New Kubernetes? by chrisandchris on Friday January 21, 2022 @10:10AM (#30024509)
If WebAssembly is the new k8s (in terms of complexity), I am going to do as much as with k8s with it: nothing.
Re:WebAssembly: The New Kubernetes? by ridiculous_leke on Friday January 21, 2022 @01:43PM (#30028065)
Off topic: I assume you have your own SaaS app. If yes, can you share more details about it?