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.
SPAs are good for some things, but those things are much fewer than what we use them for.
I'll stick to Rails though thanks :)
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!
First they do containers to replicate application servers, and now WASM to replicate bytecode server side.
In fact I consider Kubernetes much worse experience, regardless of how much hate Websphere and Co might get.
Jython is a thing.
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.
That is the thing with WebAssembly marketing, not being aware of bytecode formats history.
Java, by the way, also isn't stopping you from storing all your data in one big ByteBuffer, which is how WASM handles memory.
Jython has been a casualty of the 2 => 3 transition.
Or containers.
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.