I long for bytecode

I long for the day of bytecode, where the world of computing is not crushed under the corpse of ARM and x86. The fools can still get their shitty games, and the big studios ruled by demographic numbers can give it to them regardless of architecture. Even the OS would be mostly bytecode in this dream, only the interpreter is native, allowing for seamless ports of any system to any machine. Of course, us real programmers can use native code directly and leave the heathens to their ultra-portable Angry Birds.

I would even settle for the JVM to do this (though I would reject Java), but .NET's CLR is much nicer. Anything would be better than dealing with the outdated shitstain x86 and it's even more disgusting hack, x64, for another thirty years.

>>9
Will that instruction set be good forever? Can it be used for different processing types? For instance, if there is a break through tomorrow that allows us to skip transistors and build processors directly out of neutrons, would that instruction set be good enough? No, it would have to be redesigned, or it would have to be hackishly smeared on top of the core, much like 64bit registers on x86.

There result would be everyone ignoring our neutron processor because all the existing proprietary software only runs on x86 or ARM, and the software companies would not port it, and even if they did, the driver makers would ignore it and it would break compatibility with office printers and shit.

>>10
Not everyone of course, just the closed source companies who need 1.00 B$ to recompile software. We can sell the byte machine to them as ``increasing their market'', and people who can actually program can use the native code.