CODE WAS NOT MEANT ТО BE WRITTEN FOR A VIRTUAL MACHINE. YEARS OF DEVELOPMENT yet NO REAL-WORLD USE FOUND for having code running in more than ONE ARCHITECTURE. run your code in more than one architect

CODE WAS NOT MEANT ТО BE WRITTEN FOR A VIRTUAL MACHINE.
YEARS OF DEVELOPMENT yet NO REAL-WORLD USE FOUND for having code running in
more than ONE ARCHITECTURE.
run your code in more than one architecture anyways for a laugh? We had a system
for that: It’s called “COMPILING”.
“Yes please, don’t want to take care of the memory just asked to be allocated.”, “Who cares
how fast it is as long asit is portable?” AND “We no longer need machine code.” Are
statements dreamed up the utterly Deranged.
LOOK at what Programmers have been demanding your Respect for all this time, with all the CPU
cores and Instruction sets we built for them.
(This is REAL java software, done REAL java developers):
22222222???
“Hello would like 200 running at the same time, each one
with a different version”
They have played for absolute fools