Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
And just with the "Y2K" problem of the year 2000, it will be patched long before it becomes any kind of real problem.
Thanks. I remember the Y2K thing, the world was about to end and of course nothing at all happened.
The 32 bit on CPU (and operative systems applications) refers to the size of the registers. With 32 bit registers only 2^32 bytes of memory can be addressed, this is why 32 bit application can use only up 4 gb of ram.
But 32 bit application CAN use 64 bit variables without problem. The size of the variable is not tied to the size of the registers, we are talking of two totally different things.
The problem is only for old applications not updated anymore who still uses 32 bit variables to store the time. Even a 64 bit application will have issue if a 32 bit variable is used to store the time.
So no, Steam will not have issue in 2038 even if it remain a 32 bit application.