Happy New Years! (12)

1 Name: キタ━━━━━━━━( ・∀・)━━━━━━━━!!!! [Del]

I never thought this site would last until 2015...

2 Name: キタ━━━━━━━━( ・∀・)━━━━━━━━!!!! [Del]

2015 is five years away, idiot

3 Name: キタ━━━━━━━━( ・∀・)━━━━━━━━!!!! [Del]

Happy new year 2016!

4 Name: キタ━━━━━━━━( ・∀・)━━━━━━━━!!!! [Del]

happy new years for you guys!!!!!

6 Name: キタ━━━━━━━━( ・∀・)━━━━━━━━!!!! [Del]

>>5 Y2K is a myth, nothing will happen, you'll see.

It's just a conspiracy of the digerati to make you pay for their fixing the bugs they introduced into your systems themselves in the first place, for job security.

COBOL does the date by counting the days since 1601/01/01, VMS since −4712/01/01, and UNIX (but who still uses that anyway?) the seconds from 1970/01/01. In computers there is nothing special about the year 2000, Y2K is nothing but a big scam!

Posting from my comet-proof bunker. Hail Bob! I mean Hale-Bopp!

7 Name: キタ━━━━━━━━( ・∀・)━━━━━━━━!!!! [Del]

Isn't it Y2038 since 32bit will run out of possible dates in unix time.

8 Name: キタ━━━━━━━━( ・∀・)━━━━━━━━!!!! [Del]

>>7 Only if you use signed integer (int32) for time_t, if you use unsigned integer (uint32) and lose the ability to display dates before 1970, it can go on until 2105. Or you use a long long int (int64) for time_t, which requires a recompile of everything that links directly or indirectly to libc.

Which is why the superior DOS operating system by IBM stores the date in separate bytes for month, day, and year. It will work until the year 127 from 1900 (ie until the year 19127)!

9 Name: キタ━━━━━━━━( ・∀・)━━━━━━━━!!!! [Del]

>>8 Don't you mean 2027?

12 Name: キタ━━━━━━━━( ・∀・)━━━━━━━━!!!! [Del]

>>11 Oh infinite loops, will defun never end!

Name: Link:
Leave these fields empty (spam trap):
More options...