[spacefight]

If your system is one of those 10% and if your trading algo is executing fucked up trades because of timing issues and you lose real money - I wouldn't call that exaggerated.

Also, not sure if any of the systems mentioned in the article run JS for critical server side code.

[lucb1e]

High-frequency trading and other important realtime processes that handle money should of course be tested for this scenario (either by simply not trading for a few seconds before and after, or by properly handling it). The vast majority of the computer systems around the world are however not HFT systems and the world will continue to work normally. No Y2K-like doom scenarios needed like the article suggests.

We've been here before, June 30th 2012 also contained a leap second (see Wikipedia). The article only forecasts doom without looking back at previous leap seconds and evaluating its effect.

[ars]

> We've been here before, June 30th 2012 also contained a leap second (see Wikipedia). The article only forecasts doom without looking back at previous leap seconds and evaluating its effect.

Clearly you didn't read the article.

If you had you would have seen that they noted that last time it was on a weekend when all the markets were closed.

[kryptiskt]

That leap second pinned loads of Linux boxes at 100% CPU. I'm a customer of Hetzner, they sent out a mail asking the customers to check their machines as their power draw increased by a megawatt in an instant.