Linus himself has said Rust is pretty good and solves important problems, but also that the core kernel code is, in his view, a solved problem. They have coding standards, a history, and procedures that make the core kernel pretty damn safe.
However, the core kernel is only like 200k LOC, meaning it wouldn't be wildly impossible to rewrite it. And as for kernel drivers, many of which are not up to the same standards as the core, Rust is very viable.
Go is GCed so it is not viable for any perf-critical code like a kernel.
The planning system and data (barring military secrets) should be open source so everyone can verify the plans on their own PCs or servers. As for general security stuff, same as any bank or server system. Actually, most banks have awful security from the 90s. The labor credit system would be much more secure. Aside from that, communism would heavily disincentivize illegal hacking, and there could be a great firewall.
If a country has a communist revolution, it can host its planning and banking systems in private servers, not the cloud. Cockshott's system is much more efficient than the modern banking system, as it gets rid of huge amounts of speculation, exchange between producers, service fees, and so on. The cloud is not some kind of miracle, it really sucks in many ways. If you're just making a demo app, the cloud is probably sufficient.
I think we were talking about backend. Frontend definitely should be a functional reactive framework like Elm, ReasonML, Elmish etc. Zero runtime errors. Preferably on WebASM, or we could do as god intended and switch browser scripting to a Lisp interpreter.
Wouldn't hurt to have a standalone desktop app either, so everyone just has it in their package manager. But you could do that in QT, or we could have a new desktop GUI framework that uses FRP and data oriented programming.
I think it just depends on which component. The labor credit banking should obviously have a webapp. The numbers-crunching parts of the program are more suited to a desktop or CLI app.
Yeah, we don't live in the 80s anymore, so something particularly well-optimized isn't needed. The hardware cost really isn't an issue.
Absolutely bourgeois. This mentality is why our programs keep getting slower in spite of hardware speedups. As well, we are at like 7nm transistors now. The age of ever-increasing CPU speeds is over. We need to preserve the environment by making faster, more efficient programs and selling slower, less power-hungry hardware that lasts a long time.
Look how much slower Python, PHP, etc are compared to Go, vertx, actix, etc. Some of the best modern backend systems are literally 50x faster than Django or Rails. That means, if you have a socialist cloud service, Python users are taking up a massive amount of resources other people need.