[Galaxy Note 3 General] Sudo77:
The point still stands unchanged. If we start to develop native 64bit apps on native 64bit architectures, using 64 bit time integers now, there be less the need to go back to extend the time for all existing 32-bit applications in order for them to work. As a developer, you already should know that sometimes even going back to extend the time int for native 32 bit applications may cause them to crash due to inconsistencies and issues adjusting to the new time depending on how the app is programmed.

The Unix doomsday is expected in 2038, but doesn't need to be if we are prepared for it. We don't need to spend billions when the time comes just to fix similar to the Y2K issue. I personally care a lot about time, so I will not let this point go. Reasons being the NIST has a system of atomic clocks capable of keeping time accurate for millions of years and Unix should be able to "display" that time properly. A computer relies on accurate time management in order for it to work.

Yes... >.> I meant in general. You do not need to travel to the ends of the earth to prove me wrong LOL, but using an example with Large Physical Address Extensions is what you call it? Impressive but UNFAIR! Not that it matters, but native 64-bit architectures should be able to address a hell of a lot more RAM, even compared 32-bit with LPAE functionality.

Judging by the way you wrote this, you assumed I have a misconception. I understand this, I was hoping I was wrong in other areas. Bus width focuses on the width of diameter of the hose or straw. By water traveling down these two tubes, assumes it uses the FULL advantage of the width. Therefore more can travel through the hose at a less amount of time (64 bit instruction water LOL).

Naturally being a pump (computer) you can control how much water you can pass through the tubes. You can pass 32bit water through a hydrant hose, but what good with that do? You can just use a straw. But you CAN'T pass 64 bit water through the straw. Water water everywhere. Just like in computing, you CAN install 32 bit software on 64 bit systems, but you CAN'T install 64 bit software on 32 bit systems. Don't take the analogy too seriously, I need a WOW (get it? windows on windows) factor to help others understand the benefits not just on RAM addressing.

Ah good, more reason to wait before upgrading eh?

Interesting.

If it is bit width independent as you say, then it shouldn't matter. I am not a dev and I don't want to impose duties on others, I'm just saying lets try to keep all things native to 64 for an easier future for us all.

Let me set the stage for you of what I actually expect from beyond 4GB RAM and a stronger CPU. I work a lot with Virtualization, and I hope that one day it can come to mobile devices and work efficiently on them as well. And I don't mean VM clients, I mean actual VMs running on tablets. Imagine, no longer having to choose what you want to run on your main tablet. IOS, Android, Windows, take it all! I am also looking forward for support for large Java based and heavier flash applications to run on Android. As I hear JVM can get pretty resource intensive. Does all this want to make you throw your 32bit CPU out of the window just yet? The RAM is there when you need it. I will miss 32 bit, hell, I miss 16 bit applications, but as time progresses improvements are expected.

There is one issue though, heat... next!

I am glad we are on the same page here. :D Until next post then.