So these would still have been bugs under the JVM too - crashing from an out-of-bound array access or failing to allocate a stupendously large number of objects. The JVM would stop them from turning into potential arbitrary code execution, though (as some, but not all, of these bugs did).
That will take a while. And even then, people will likely keep using 64 bits for most things.
(Please don't make the obvious reply.)
< simcop2387> farnsworth: eta[16 EiB, 19200 MiB/s] - #now# -> "years"
< farnsworth> simcop2387: 2177.63532452879 years
based on marketing info on DDR4. So at the very least it's going to take a while before we even have to worry about a max of 16EiB in address space.But, it takes longer each time. With exponential growth (e.g. Moore's Law) then you use up bits linearly. If you double every two years, then you use one bit every two years. That means we have about 32 years from when 32-bit became inadequate to when 64-bit becomes inadequate.
We currently have supercomputers with tens of gigabytes per processor and tens of thousands of processors. Already up to 51 bits. We're also working out fast persistent storage like NVMe and crosspoint that allow us to attach a board with terabytes where we used to attach gigabytes of DRAM. Combine those two and you can max out a 64 bit address space with current technology, let alone tomorrow's technology.
Then again, super computers aren't really running the same architecture as the rest of us.
> Then again, super computers aren't really running the same architecture as the rest of us.
Sure, but there are pushes to make datacenters act more like a giant computer, so there are niceties to a shared address space that aren't restricted to traditional supercomputers.
I'm a pretty high-level language user (read: I don't do C, et al), so when I read stuff like this it always makes me cringe and be happy Hickey decided to keep it simple. 64 bits, everywhere! (God save us when things go to 128)