Abolish Unix time.
>>107003465We need to start counting seconds from January 1, 1936 or from January 1, 2025 instead of using 1970, it makes no sense.
>>107003465what do you suggest we use instead?
>>107003465>weeb has shit opinions nothing new here
>>107003465https://en.wikipedia.org/wiki/Year_2038_problem#/media/File:Year_2038_problem.gif
>>107003900>big corpo cant be arsed to keep their ducks in a row bc theyre fucktardedmore news at 11not a problem with a 64 bit value
>>107003465y tho?
>>107003900>Resurgence of Y2KAnother nohtingburger.
>>107003900>Most operating systems designed to run on 64-bit hardware already use signed 64-bit time_t integers. literal nothingburger
>>10700346532 bit unix time works until 2038 which is around 67 years since 197064 bit unix time is 2 billion times bigger than 32 bit, meaning it can lasts 67 * 2 billion years or 134 billion CEwe are now in 2025, so it's still billion years until we run out of 64-bit unix time, OP
Windows time goes up to the year 30827 while being more precise (100 nanosecond resolution) than Unix time (only 1 second resolution). Yet another example of how Linux copied a shit boomer design from the 1960s and it came to bite them in the ass.
>>107004509>nanosecond resolution on Linuxwhat is clock_gettime(CLOCK_REALTIME) tv_nsec?
>>107004151i was about to say that it'll be interesting to see what all the internet of shit gadgets will do, but the most likely scenario is "nothing", as the norm for them
>>107005168going back to the 1900s is a feature, not a bug
Make UNIX Time into 128bit
>>107003465We could use the same epoch for unix 1761350400 and stardate 20386
>>107003465unix has timeformatdoes bendix have timeformat
