Microsoft Invents The Y2K10 Bug

Hard to believe anyone could stuff up a simple change of decade
<http://news.zdnet.com/2100-9595_22-378427.html>.

 

As opposed to linux which completely loses the plot recording uptime
after 497 days.

Glass houses, stones and all that stuff.

 

[email protected]:~ # ssh mink uptime
12:03am up 1150 days 4:32, 0 users, load average: 0.00, 0.00, 0.00
^^^^^^^^^

 

Of which there are a LOT around - including several hundred in a penguin
colony in which I have a professional interest.

 

Decade changes next year

 

Not according to the usual convention.

 

Yet your “professional†interest doesn’t extend to keeping them up-to-date.

 

Lack of testing.
I tested my date subroutines for every day in thousands of years by
calling them with consecutive day numbers (and dates) and checking
that the answers were still one day apart.

 

Nope Ms Windows does not do 0 for the first device.

I like to use 0, meaning the first in a conversation. That gets some brains
working. Under the radar for the rest

 

Let it go. The kernel has moved on.

Now tell us all about the 2038 problem Linux faces

 

What convention is that?

First decade was 1-10, second 11-20, keep going and its 2001-2010, then
2011-2020.

Same discussion happened at the incorrect change of millenium 10 years
ago...

 

It extends to recommending that something be done, however it does not
extend to having the ability to authorise something being done. There
are also issues involving certification of the whole OS and app package,
and I understand nothing newer has been certified to the satisfaction of
the auditors.

 

There was never a year 1 AD. The Gregorian Calendar wasn’t introduced until
1582.

 

What 2038 problem?

 

You’re talking about a kernel which was obsoleted 6 years ago.

 

But the Gregorian calendar system, as updated over the centuries, has
renumbered the prior years. So now we have 1 BCE and 1 CE and no year
0. So decades, centuries and millennia actually start at 1, not 0.

 

But AD and BC refer to the birth of Jesus, who was age 4 (at least) in
1AD. King Herod was the ruler during the time of the Nativity, and
Herod died in 4BC. So we may as well say the millennium started in the
year 0. Just because some moron got it wrong a couple of thousand
years ago doesn't meran we have to keep it that way.

 

Wrong, AD and BC are not the designations used for calendars any more.
The correct usage is CE = Common Era and BCE = Before the Common Era.
The birth date or not of Jesus Christ is completely irrelevant to the
calendar system, as it is not based on his supposed birth date any
more (or even on his existence or not). The current definition of how
the calendar system works says that there is 1 BCE and 1 CE and no
year 0 in between. So, by definition, there is no year 0. There is
nothing clearer than that - year 0 does not exist, by definition.

 

Why should we follow a definition decided by morons?
When measuring time it is necessary to starting timing from zero.

 

That convention was from the days when Europeans didn’t understand the
concept of 0. I would hope they’ve made some progress since then...