[0x000xca0xfe]

Why not? Emulation is a beautiful thing. It makes one realize that CPU instructions are just another form of abstraction. Providing the old APIs/ecosystem is usually harder than just emulating the binary.

And running old software on modern hardware often uses only a fraction of the power the old hardware used to need. If one cares about power consumption, modern software has become so much worse.

[bullen]

Well, if you include the power to get to the modern hardware: no; then you are indebted forever by running Starcraft on emulation.

We often discount progress as obvious because we never paid the price of photosynthesis for millions of years before our tiny part in existence.

My problem is specifically getting to the consensus we have today, we were too slow, 6502 (8) freed humans 1982-85, 68000 (16) and ARM-1 (32) came 1985. So we had the instructions (in both senses) for the final hardware then.

40 years, and X trillion barrels of oil, later we are still in complete hardware and software confusion.

64-bit is a big mistake, because nothing scales to infinity; and since nothing is free, we are about to pay the price now!

Indebted to the past and the future to max!

I say roll back to C and Java and rebuild from there on Risc-V (even if it has 128-bit addressing, in case you run out of your 18.4 exabytes 64-bit RAM/disk).

But it might already be too late.

[0x000xca0xfe]

You should try working in embedded software; it has all the C code and 32-bit addresses you could ever wish for.

[bullen]

I would if they made micro controllers that had better hot-reload.

Also would need more cores, SRAM and some OpenGL ES GPU! ;)

[thfuran]

C is crap that only exists because it has always existed. Why would you want to reboot the world on C? And why java as the only alternative rather than something more different?

>64-bit is a big mistake, because nothing scales to infinity; and since nothing is free, we are about to pay the price now!

What?