Ummm... I'm not sure what the point is? And why that's stated as a response to my post?

I got the chunks wrong, I thought they were bigger than 16x16x128.

From your second link:
"If you go outside that range (about 25% of the distance from where you are now to the sun), loading and saving chunks will start overwriting old chunks. At a 16/th of that distance, things that use integers for block positions, such as using items and pathfinding, will start overflowing and acting weird."

That's basically what I said - you could go several orders of magnitude farther than the surface of the earth, before the game engine will start having problems. Now, I'm not sure what [distance-between-earth-and-sun]/64 is, but I am pretty sure it fits my approximation of "several orders of magnitude more than the surface of the earth".

If you're just illustrating that on top of Java being a bad influence on the optimization, there's also lack of proper optimization work done by Minecraft devs, I never denied that either.

"Far Lands" got fixed a while ago btw.

I appreciate some of those links because they're informative, but I just don't get what you're getting at?