Skip to content

Comment on Microsoft confirms Exchange Year 2022 problemparent

Comments

Because these files aren't going backward in time, and it's quite unlikely this code will be in use in 78 years.

Well clearly they didn’t even seem to expect this code to be in use in 2022!

it's quite unlikely this code will be in use in 78 years

Famous last words.

I know of a system that uses "1/1/2099" everywhere an "infinity" date is needed.

The problem with fixing it, is nobody thinks it will be their problem.

My employer uses the year 2041 for infinity. It will be a truly massive disaster when that year arrives. There is tens of millions of dollars of advertising spend that is paused until “infinity”.

Whenever advertising stops working, the world becomes a better place.

As far as I understood, according to soared's comment, a lot of advertising campaigns will _start again_ in 2041.

Realistically these particular people are right though.

Unless you're importing historical records...

It seems likely that this is an issue with the code specifically, rather than the encoding of the files, based on the fact that they managed to roll out a fix pretty quickly.

I agree, but parent was responding to a more general comment of "Why is anyone using two-digit years anywhere at all?".

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.