The end of time is coming in 2038, where every single 32 bit time integer will overflow and throw us back to 1901!
https://en.m.wikipedia.org/wiki/Year_2038_problem
Y2K all over again?
Will fucking nothing happen this time too?
>>51496889
Who cares? In the year 2030 the computers will be solving all problems.
>unix literally has planned obsolescence built in
>>51496905
yup, just like Y2K, but this time more fatal. all embedded systems dude
>implying this won't be largely solved many years in advance
>>51496905
yep.
>>51496934
Sum up why I should care.
During Y2k stupid faggots were saying that toasters would fly through the air and kill people.
What the hell is this going to do? Why should I care what the date in my car's embedded computer is?
>>51496889
>make new programs
>if current_year<=2015
>current_year+=2038-1901
there you go OP
>>51496959
oh idk bring the net down?
>>51496985
And how is it going to do that?
If you clock's batteries run out I guess that means time stopped too huh?
>>51497006
all tls/ssl traffic will stop because no valid signed keys, ssl/tls aint doing shit without keys
all activation keys are fucked, so are licenses
>>51497042
I don't really see a problem
You think people cant solve something so trivial in the next 20 odd years?
Did you know that home computers as you know them have only been around for a little over that long?
>>51496918
>planned
Ok. So I won't use and 2015 tech in 20 years
Thanks for the heads up.
>>51497042
what software that needs an activation key that you run right now do you plan on using in the current version in 2038 ?
and we can and will just sign new certificates.
so how do we fix this?
>>51497062
almost any arm system will fail, as they are all 32bit based so far, that means planes, airports, cars, boats also systemas such as banks, the stock market, hospitals, police depts, 911, etc.
Think about it dude. You cant fix a 32 bit int once it overflows. Its as you want to use 4+GB of ram on your PC. Not happening
>>51496889
>2015
>still care about clocks
>don't solder CPU already
>>51497127
using 64bit variables to store values
>>51497137
So, murderous toasters flying through the air? Gotcha.
I'll let the boys down in the lab know they have 23 years to work on it.
>>51497162
which means full global 64 bit upgrade. Everything.
>>51497162
Isn't that just delaying the problem?
>>51497137
or you just update the constant from where it starts counting.
problem solved
and you can easily use 4+gb of ram on a 32bit computer. i have 6 gb with an athlon 3000+
>>51496905
y2k was a nonproblem except for the most retarded implementations
2038 is an actual problem for all 32 bit chips
>>51497172
dude you cant. there is no way other than hardware upgrade to 64bit and full software rewrite and reprogram of any embedded system. which means all emedded 32bit systems become paperweights after 2038
>implying I'll be alive
>>51497162
How about we stop using primitives to track things that don't have a defined range?
>>51497127
Remove the 32bit time functions from the standard library. Every program that fails to compile will need a patch.
It should only take about a year for the open source world to transition. Windows will take years.
>>51497232
So lets start over.
What do you think I will be using in 2038 that wont be at least 64 bit?
Do you seriously think we wont be on x128 or some shit by then? x86-64 will be old trash by then.
>>51497248
you are forgetting that it will take 50 years for that update to hit any debian boxes
>>51497248
my man with a brain
which means 1+ year with no computers
>>51497248
>Windows will take years.
what ? no ! they need their 32bit timer counter to adjust the color of their scrollbars in their kernel. they can't remove that !
>>51497272
I'm sure they'd give something like that priority and get it out in 30.
>>51497162
Guys!
What if, you know, we didn't have count seconds since some arbitrary date to keep track of time in computors?!?
>>51497272
cca 70 for Ubuntu lol
>>51497292
Cant they just pay a shitload of poo in loo niggers to make new code for it?
Can't they do that with all of their depreciated garbage?
>>51497266
> x128
wtf is x128 ?
if you are talking about 128 bit cpus, we already had them.
if you are talking about another x86 extension: nope, that won't happen.
>>51497301
The standard SI unit for time is second, so no
>>51497318
>wtf is x128 ?
How the fuck should I know, I cant see the future.
That's why I asked you.
>>51497301
and how would you do that ?
do any of the irretrievable space probes depend on clocks and run on 32 bit?
>implying I wont have committed sudoku by then
>>51497363
90% lol
>>51497187
292 million years in the future are enough time for a good plan.
>>51497398
I meant 219 million years, sorry for that.
>>51497248
This is a *nix problem, Windows never had this issue in the first place. Windows generally avoids single-number timestamps, but when it does it counts .1 millisecond intervals from January 1st 1601. This number needed to be 64 bit for quite awhile.
>>51497398
>>51497417
You'll all still complain in 219m years
>>51497465
The problem is anon, programs still use the standard C library even if they're windows applications.
t. msvc***.dll
>>51497516
There's only one man who truly knows clocks well enough to save us.
What are we going to do in 2147485547, /g/?
>>51496889
Nerve gas 2038?
>>51497700
I fucking kekked
Wpuldnt this be a non-isdue with 32 bit client-server systems? If the NTP server is x86 and the client machine is x86, and the server is also x86, then wouldnt they all just sign the keys using a 1901 date? this would still make them valid amongst x86 systems. Its the x86-64/x64 based systems that are gwtting shoveled.
Or am i missing something?
>>51498086
this is exactly why we should stick to x86. fuck x64 and fuck those with 4+gb of ram
https://en.wikipedia.org/wiki/John_Titor
Quick, /g/, get Titor that IBM 5100 already
>Titor had been sent back to 1975 to retrieve an IBM 5100 computer which he said was needed to "debug" various legacy computer programs in 2036; a possible reference to the UNIX year 2038 problem. The IBM 5100 runs the APL and BASIC programming languages.
>>51497232
I can make a clock that works well past 2038 using a 8bit µC.
Just use an into per digit...
Ad 5/6 digits in a struct for the year, 2 for everything else...
>>51498261
Int, add.
Fucking spellcheck.
Also, if you want Unix time, then you can still make a struct grouping several ints (or charts) and overflow to the next one...
>>51498185
0/10
>>51498255
STEINS;GATE
