I entirely agree, this would be great. I don't see why it has to be done in cities though. Farmers in smaller co-ops can provide a similar decentralisation.
I don't really understand the whole "urban agriculture" crowd.
People do often live in crowded cities, but there's plenty of space to grow stuff on outside of cities. It's the same kind of thinking that gave us the solad roads (which were, predictably, a catastrophic failure).
> Does the whole RISC Vs CISC of X86 and ARM make a difference?
Not really. Arm hasn't been RISC for quite a while now (there's a "Floating-point Javascript Convert to Signed fixed-point, rounding toward Zero" instruction(!), SIMD, etc etc).
The difference can be explained partially by the memory model: x86 has total store ordering, which can be slower than Arm's weak memory model (it allows the hardware to be more creative).
> running native compiled code
There's more to it than 'running native code'. It depends a lot on what code is running (any CPU implementing the above javascript instruction would be much faster on a web benchmark for example). It also depends on the compiler. If the code is control-flow heavy, there isn't much to do except having large cache sizes and wide pipes, which most high-end, out-of-order CPU do already.
This looks great, thanks! It looks very easy compared to subprocess.run and friends. I hope it'll help convincing my colleagues to default to python instead of bash (or, heavens forbid, csh)