Slashdot Mirror
Big Tech Warns of 'Japan's Millennium Bug' Ahead of Akihito's Abdication (theguardian.com)
MightyMartian shares a report from The Guardian: On April 30, 2019, Emperor Akihito of Japan is expected to abdicate the chrysanthemum throne. The decision was announced in December 2017 so as to ensure an orderly transition to Akihito's son, Naruhito, but the coronation could cause concerns in an unlikely place: the technology sector. The Japanese calendar counts up from the coronation of a new emperor, using not the name of the emperor, but the name of the era they herald. Akihito's coronation in January 1989 marked the beginning of the Heisei era, and the end of the Shwa era that preceded him; and Naruhito's coronation will itself mark another new era. But that brings problems. For one, Akihito has been on the throne for almost the entirety of the information age, meaning that many systems have never had to deal with a switchover in era. For another, the official name of Naruhito's era has yet to be announced, causing concern for diary publishers, calendar printers and international standards bodies. It's why some are calling it "Japan's Y2K problem." "The magnitude of this event on computing systems using the Japanese Calendar may be similar to the Y2K event with the Gregorian Calendar," said Microsoft's Shawn Steele. "For the Y2K event, there was world-wide recognition of the upcoming change, resulting in governments and software vendors beginning to work on solutions for that problem several years before January 1, 2000. Even with that preparation many organizations encountered problems due to the millennial transition. Fortunately, this is a rare event, however it means that most software has not been tested to ensure that it will behave with an additional era."
Unicode's Ken Whistler wrote in a message earlier this month: "The [Unicode Technical Committee] cannot afford to make any mistakes here, nor can it just *guess* and release the code point early. All of this is pointing directly to the necessity of issuing a Unicode 12.1 release sharply on the heels of Unicode 12.0, incorporating the addition of the new Japanese era name character, which all vendors will be under great pressure to immediately support in 2019 software releases."
Unicode's Ken Whistler wrote in a message earlier this month: "The [Unicode Technical Committee] cannot afford to make any mistakes here, nor can it just *guess* and release the code point early. All of this is pointing directly to the necessity of issuing a Unicode 12.1 release sharply on the heels of Unicode 12.0, incorporating the addition of the new Japanese era name character, which all vendors will be under great pressure to immediately support in 2019 software releases."
When Jesus comes back do we need to reset the year back to zero? Crap, as a programmer I hate our calendar system(s)!
"I have never let my schooling interfere with my education." - Mark Twain
n/t
"the official name of Naruhito's era has yet to be announced"
Then... just announce it?
And let those gaijin be right? That's unpossible!
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Japanese regnal years are not used for any significant calculations. Behind the scenes it's YYYY, with regnal years used only for display. This is an aesthetic issue only, and hardly unforeseen.
And I'm a throwback apparently for using BC and AD ...
And you had to go and ruin it. Let us never speak of this again.
Time to offend someone
Said the entire world to America re Metric... but hey who's keeping track...
Officially years in Japan start with 1 and the coronation of the new emperor. Now it seems that the year in Japan is Heisei 30, which means it's the 30th year since the Heisei emperor (Akihito) took the throne. This would be something like in the US calling 2016 as Obama 8 or 2018 by the term Trump 2. The real problem here isn't that computers are going to shut down in Japan when the current emperor abdicates next year as planned. This isn't really a Y2K problem. The Guardian usually does good work but to say this is similar to Y2K is just not correct. The article even admits that some older computers have actually never updated the year from the Showa era (when Hiirohito was emperor) so they think this year is Showa 93. Those computers will have a problem in 2025 as their calendars were never designed to hold 3 digit years, which would make 2025 be Showa 100. The real problem with the abdication is that the next era for the upcoming emperor has not yet been named. OK, so why is that a problem? Well, Japan has a history of creating a brand new character for the era when it change and Unicode has a major release scheduled for right before the abdication is scheduled to happen. The brand new character is the problem because the next release of Unicode won't support it because nobody knows what it will be yet. They have the ability to guess, but nobody wants to guess because they could be wrong. So all this hubbub is that next year's major Unicode release will require a patch shortly after release with the patch including the new character for the new era. Do keep in mind that Akihito could die of natural causes before the abdication and this problem will happen immediately upon his death. And this problem will happen every time a new emperor takes over. I'm not convinced that this is really a major problem. Computers could easily just show Heisei 31 and so on until the Unicode fix is in place. I guess it's just fun on a slow news day to blow things out of proportion.
will they also fix the 2038 bug as well?
or hold off so they have jobs in 2037 fixing it.
Well, I've always thought the International Fixed Calendar [wikipedia.org] was a decent attempt at sanity, but if there's people in the world that can't adopt the metric system, there's no way in hell the calendar could change.
Maybe the best solution is to use a sane calendar system similar to that one as a base system (similar to Universal Coordinated Time) and then just calculate offsets into whatever crazy calendar system some group prefers to use.
Our current calendar system is pretty much bonkers anyway. We seem bizarrely attached to concepts like a 7 day week which is familiar but totally arbitrary. You could have a year with 73 weeks of 5 days each or a year with 5 months of 73 days and it would be equally valid and equally arbitrary. It's never been clear to me why we need to worry about keeping months coordinated with particular seasons. So what if Christmas in the northern hemisphere gradually drifts to summer over the course of a few hundred years?
I've always liked the concept of metric time too.
Meiji, Tasisho, Showa, Heisei. Add new name, date counter goes back.
Domestic spying is now "Benign Information Gathering"
Only Japanese? We are at Jesus 2018.
Have gnu, will travel.
"Akihito has been on the throne for almost the entirety of the information age"
Umm, no. We were well into the information age by 1989. The use of computers in vital infrastructure (e.g. banking) dates back to the late 50's. I checked out the author of the article, and as expected, he appears to be under 30; this would explain his myopic view of history.
"...Unicode, the international standards organisation which most famously controls the introduction of new emojis to the world."
This is a new level of cluelessness. "Most famously"? Like, internationalization and localization were just afterthoughts; it's the emojis that they really focus on.
How is this guy a technology reporter for a major newspaper?
Actually it's not the Shwa era, but the Showa era, with a bar on top of the o. The character in question (U+014D) is used in transliterating Japanese in Latin script to indicate pronunciation. It has been part of Unicode since 1991.
It's interesting to see in the summary a discussion of Unicode 12.1 vs. 12.0, when Slashdot itself doesn't support the Unicode 1.0 characters necessary to write the summary :)
As a state gets corrupt, its laws multiply; the most corrupt states have the most numerous laws. (Tacitus, Annales 3:27)
Metric is crap. "But muh 10s!" Whatever. Computers have no problems with calculations (nor do most people), and I'd rather have a measurement meaningful to people than easily divide. I'm almost never converting inches to yards, but if I do it's just divide by 12 * 3 = divide by 36. Sure I could convert meters to decametres slightly faster in my head... but why? Also, I'd like to continue to name the temperature without going into decimals. It's much nicer to say "It's 91 degrees out" than "It's 32.78 degrees out."
There's really no argument in using metric other than "But everyone else is doing it" and "Everything divides by 10!" For me, the usability and perception of imperial units are more meaningful. They were defined without needing an external reference to understand or measure roughly.
7 day weeks are speculated to have been based on the lunar cycle from the ancient Babylonians.
Assuming that is true for argument's sake, what relevance does it have to modern life?
Regarding a non-7 day week, this has been tried before and didn't work.
Just because a small group tried something a long time ago doesn't have a lot of relevance to the discussion. Maybe it just wasn't the right system or the right time to do it. There is nothing magical about a 7 day week. It's fine but we could easily have a 6 or an 8 day week and there is no objective reason that couldn't work just as well. It's just something we continue to do because we've done it that way for a long time. The major benefit of it is that most of the world has standardized on it which probably outweighs most drawbacks but that doesn't mean that it is optimal or couldn't be improved upon. The real question is whether an improved calendar would result in benefits that outweigh the costs.
Sometimes a long-followed social construct has survived because it works well for us animals
Just because something worked reasonably well in the past is not a valid justification for continuing to do it that way in the face of a better alternative. "That's the way we've always done it" is one of the worst and most expensive arguments people routinely make. Tradition is a fine thing and standards are a good thing but only to a point. Now you could sensibly argue that any of the calendar improvements we could make are well into diminishing returns as far as improvements go and thus not worth the cost but one should not blindly assume that to be true.
My suspicion is that the calendar won't be changed again (if it ever is) until after we become a multi-planetary species. It would take a major event to get everyone to agree to change calendars so everything I've said is purely conjecture.
I still want to strangle the coder who thought it would be a good idea to use a SIGNED integer to count seconds in the epoch.
Like time's gonna run backwards soon? Bloody Nitwit. You HAD 32 bits - Why didn't you use all of them?!?! GRRR
AC
The Soviet Union is a rather large testing ground. They tried variations of 5 and 6 that worked poorly in an attempt to avoid using 7, which they viewed as a number that made it too easy for people to hold on to religion.
The Soviet Union tried a lot of things that didn't work very well. This is pretty far down the list among them. Plus like most standards it's the network effects of the existing standard that makes them hard to change once they are well established.
While there are certainly an infinite number of variations one could try, its not like France (in the reference I cited) or the Soviets were too small a sample size to pretend that we have no evidence of relevance that 7 isn't just an arbitrary number and any other would work fine.
Those are interesting case studies but one would have to dig a lot deeper into the reasons for those failures to determine if the length of the chosen week was the proximal cause of the failure. My guess is that it failed for other reasons similar to how the metric system has to date failed to take hold in the US. Just local political and economic and network effect realities that made changing problematic. There is no objectively obvious reason a 7 day week should be preferable to any other similar length week and what evidence we have in relation to it is relatively scant. Main problem is that it's hard to test alternatives in the real world on a large scale.
To change it would be monumentally expensive, disruptive, and really would replace it with something else just as arbitrary.
Certainly. That doesn't mean doing so isn't a worthwhile exercise. My whole point is that our current calendar is unarguably illogical, flawed, and occasionally problematic. We use it because of network effects, not because it is an optimal system.
In other words, at least until we start colonizing other worlds with other chronological cycles, it will persist.
Agreed and I said more or less exactly this in a different post in this thread. I think it would take something like us becoming a multi-planet species to be a big enough jolt to the system to make it worthwhile to change calendar systems. Maybe not even then but I'm not sure what else would be sufficient cause.
This is just stupid.
http://www.acetonestudio.com
TLDR: Time is that way for a reason, and you should have a healthy respect for it.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
Not nearly so well as the Japanese calendar.
Imperial / U.S. Customary units work great - until you need to perform even the simplest calculation, at which point you get subjected to mild torture grinding through arbitrary unit conversions, or have to deal with scientists, engineers, anyone anywhere else in the world - at which point you invoke some much uglier unit conversion torture that relies on knowing the conversions between units you use commonly, and units you rarely use in a completely different system.
--- Most topics have many sides worth arguing, allow me to take one opposite you.
Just checked some packaged food, and the "use by"/"best before"/"packed on" dates are in Heisei Era on all of them. Some have both Heisie and CE dates, but none have CE only.
What exactly is the point in having a calendar that's not synchronized to the solstices?
There is no objectively important reason that a calendar that tracks rotations of the Earth has to have any relationship whatsoever to orbits around the Sun. There is some utility in doing so but it's not as if we would be unaware of and unable to plan for the fact that the Earth takes approximately 365.25 days to orbit the Sun. Heck for quite a long time we used the Julian calendar and it worked pretty well overall despite not quite so accurately reconciling the length of a year to the length of a day. The length of a year doesn't care how we bother to subdivide it.
Clocks measure time elapsed since an arbitrary epoch - calendars subdivide a year so that you can schedule seasonal activities.
You are conflating two unrelated things. Calendars measure time in relationship to arbitrarily chosen celestial cycles. A day measures the rotational time of Earth and a year measures the orbital time of Earth around the Sun. There is no reason we necessarily need a calendar to reconcile orbits around the Sun with rotations of the Earth. They are separate and arbitrarily chosen events with no causal relationship between their lengths. It is a useful exercise to do so but a useful calendar can just measure the passage of days with relation to a different cycle (the lunar cycle for example) and be just as valid. And having a calendar that has arbitrarily varying sub cycles (months over varying lengths) does not add to its practicality or make scheduling easier.
An accurate clock can't even measure the passage of days correctly, since every day is, on average, slightly longer than the one before it thanks to a combination of solar and lunar tidal drag, along with other forces that are less well understood
That argument is self defeating. If an accurate clock couldn't measure the passage of days accurately then we wouldn't be able to tell that the length of a day changes. That said, it is not objectively necessary to change the definition of a day to match Earth's current rotational period. In fact if we are on a different planet it would be impractical to use Earth's rotational period as the basis for calendar scale time keeping. Furthermore the length of a year (an orbit around the Sun) is also changing because of the n-body problem and changes to Earth's orbit.
Why not put the era names in a separate config file? The logic won't change, but the list will be added to until Japan's population grows extinct.
Why does every era have to have its own codepoint? It's just a name, isn't it composed of existing glyphs?
False comparison.
While imperial units might be a little amusing, at least we all know precisely how many millimetres there'll be in an inch next year or a hundred years from now.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
If this is a problem for unicode, then at least one of the calendar and unicode are total shit.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
Who the heck moderated this Funny?? It's an Informative important correction to the Summary!
You're welcome to keep your imperial system if you're so attached to it, nowadays us outsiders have more incredible things to laugh (or cry) at in the USA anyway, but what you write is nonsense.
There's really no argument in using metric other than "But everyone else is doing it" [...]
In other words, it is a widespread standard. Isn't that a pretty solid argument?
For me, the usability and perception of imperial units are more meaningful. They were defined without needing an external reference to understand or measure roughly.
In daily life that 'external reference' is irrelevant. You can just as easily have an intuition about metric units as about imperial units.
And people rarely think in non-integral degrees celcius unless they're doing science.
I'm almost never converting inches to yards, but if I do it's just divide by 12 * 3 = divide by 36. Sure I could convert meters to decametres slightly faster in my head... but why?
There's really no argument in using metric other than "But everyone else is doing it" and "Everything divides by 10!"
And, as you yourself said, it's faster to do the conversions in your head.
Also, I'd like to continue to name the temperature without going into decimals. It's much nicer to say "It's 91 degrees out" than "It's 32.78 degrees out."
That's some pretty impressive trolling. The precision of Celsius degrees is a little over half the precision of Fahrenheit degrees. To get the same precision, you would only have to add 1/2 when necessary. Even so, I doubt most people can distinguish temperature to that precision without using a thermometer anyway, so there isn't any need to use fractions of a degree in normal conversation.
I've got a hot water tank with an internal space that's 60cm x 90cm x 200cm. What's the volume of water that it contains? What's the mass? How much energy do I need to heat it from 20 C to 50 C?
0.6 * 0.9 * 2 = 1.08 cubic meters, of 1080 litres, which will weight 1080 kg give or take a few grams depending on water quality.
To heat it 30 degrees, I'd need 1080 * 30 = 32,400 kCalories, but you probably want it in Joules, so you do have to multiply it by 4.1868 (wow, I hate having to multiply things by weird values to convert stuff!) = 135,062.64 kJ . Let's call that 135 MJ, because using too many significant figures is stupid. If we want to heat it using a 240V, 13A supply, that can output a maximum of 240V x 13A = 3120W or 3.12kW of power, so it will take 135 000 000 / 3120 = 43 000 ish seconds, or 12 hours.
That's clearly not acceptable, so I'm going to rip that crappy hot water boiler out and throw it in the back of my truck. I forgot to empty the water out, and the water is almost all of the weight, but I am Superman so I easily tossed it out of a second story window 5 meters above the ground. Crap; I should have checked what was underneath. That tank will be going at sqrt(2 g s) m/s when it hits the ground - 10m/s! It will have the energy of 5m*1080kg*g = 50 kJ; if that energy were absorbed by the rear shocks in my truck in one second, they'd make a hell of a noise. I guess the most noise they could make would be 10log(50kW/10^-12W); that's just shy of 170 dB. i should definitely apologist to my neighbors...
I'm not much of a fan of base 10, but it's what we've decided to count in. It'd have been nice if we counted in 12 or 60, but we don't. Before you go claiming that "metric is crap" I'd like to see you do the above in imperial units. Use nice round starting values if you like, like 2ft x 3ft x 6ft. Go on.
Some Traditions ok to continue, like bowing , which is a fine substitute for hand shakes, kissing, etc... but using a persons anointed position date costs largely outweigh the nostalgic benefits. Japan has much bigger issues to confront. Scratch this one off the list.
The computers are all on a superior calendar. One based on the Epoch, January 1, 1970. That's when life began as we know it. So all we have to do is publish a correction to the TZ data and be done with it.