As long as the kernel keeps supporting loading and executing processes with 32-bit code, they don’t even need to go that far. There shouldn’t be much stopping Valve from just supplying libraries themselves inside a container. In fact, that’s what the Steam Linux Runtime “Sniper” does.

TypeScript […] only adds syntax, and doesn’t re-write it.

I believe enum, const enum, and decorators would like to have a word with you.

Swift also uses backticks and Rust has a dumb one in the form of r#thekeyword. Still much better than introducing a async as a new keyword in a minor version of a language and breaking a bunch of libraries.

Rust is verbose, but C++ might still take the cake with its standard library templates. Especially when using fully-qualified type names…

auto a = ::std::make_shared<::std::basic_string<char, ::std::char_traits<char>, MyAllocator<char>>>();

A reference-counted shared pointer to a string of unspecified character encoding and using a non-default memory allocator.

This means either them or more junior developers will be brought in as glorified prompt engineers.

Oh, sweet summer child. It’s not going to be junior developers; they still have self-worth. An un(der)paid intern or outsourced contractors, however? They’re fine working for scraps and no health insurance.