The article does mention a few areas of interest: - Languages with "better" (=more modern hardware friendly) loop constraints are easier to parallelize (Fortra

The article does mention a few areas of interest: - Languages with "better" (=more modern hardware friendly) loop constraints are easier to parallelize (Fortran, Erlang, …) - CPU architectures with better programmable vectorization (ARM SVE, Risc-V VE) are much easier to work with, if the language primitives allow it (see above) Porting software over to fortran/erlang on aarch64 is something you can already do today, if you want to. Rust/Zig/etc. and RISC-V could have a good opportunity here to figure out better ergonomics for vectorization and more hardware friendly cache coherency policies, too, but no clue if anyone in the relevant standard gremiums cares. In terms out "but what can I easily use as drop-in replacement?" Yeah, we're kinda stuck with C and languages that inherit its problems (current Rust/Zig/etc. included).