Editing Talk:2697: Y2K and 2038
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 7: | Line 7: | ||
Somewhere there is an essay about the unexpected synergy between the Y2K bug and the burgeoning open source movement, which may or may not be useful for the explanation. [[Special:Contributions/172.70.214.243|172.70.214.243]] 20:18, 11 November 2022 (UTC) | Somewhere there is an essay about the unexpected synergy between the Y2K bug and the burgeoning open source movement, which may or may not be useful for the explanation. [[Special:Contributions/172.70.214.243|172.70.214.243]] 20:18, 11 November 2022 (UTC) | ||
− | |||
:https://www.livehistoryindia.com/story/eras/india-software-revolution-rooted-in-y2k is a fascinating essay too. [[Special:Contributions/172.70.214.151|172.70.214.151]] 21:03, 11 November 2022 (UTC) | :https://www.livehistoryindia.com/story/eras/india-software-revolution-rooted-in-y2k is a fascinating essay too. [[Special:Contributions/172.70.214.151|172.70.214.151]] 21:03, 11 November 2022 (UTC) | ||
:I wouldn't be surprised if there's such an essay, but I suspect it's more of a coincidence. The late 90's was also when the Internet was really taking off, and that may be more of a contributor. [[User:Barmar|Barmar]] ([[User talk:Barmar|talk]]) 23:04, 11 November 2022 (UTC) | :I wouldn't be surprised if there's such an essay, but I suspect it's more of a coincidence. The late 90's was also when the Internet was really taking off, and that may be more of a contributor. [[User:Barmar|Barmar]] ([[User talk:Barmar|talk]]) 23:04, 11 November 2022 (UTC) | ||
+ | ::All involved what epidemiologists call coordinated or mutually reinforcing causes, IMHO. [[Special:Contributions/172.71.158.231|172.71.158.231]] 01:41, 12 November 2022 (UTC) | ||
− | |||
− | |||
Speaking of which, what comes after Generation Z? Generation AA? ZA? Z.1? Help! [[Special:Contributions/172.70.214.243|172.70.214.243]] 07:24, 12 November 2022 (UTC) | Speaking of which, what comes after Generation Z? Generation AA? ZA? Z.1? Help! [[Special:Contributions/172.70.214.243|172.70.214.243]] 07:24, 12 November 2022 (UTC) | ||
:{{w|Generation Alpha}} [[Special:Contributions/172.69.34.53|172.69.34.53]] 07:27, 12 November 2022 (UTC) | :{{w|Generation Alpha}} [[Special:Contributions/172.69.34.53|172.69.34.53]] 07:27, 12 November 2022 (UTC) | ||
::[[1962|Zuckerbergs Army.]] --[[User:Lupo|Lupo]] ([[User talk:Lupo|talk]]) 15:18, 12 November 2022 (UTC) | ::[[1962|Zuckerbergs Army.]] --[[User:Lupo|Lupo]] ([[User talk:Lupo|talk]]) 15:18, 12 November 2022 (UTC) | ||
− | + | ||
− | |||
I've been unable to confirm this so I'm moving it here: A major problem had struck IBM mainframes on and after August 16, 1972 (9999 days before January 1, 2000) that caused magnetic tapes that were supposed to be marked "keep forever" instead be marked "may be recycled now."{{Actual citation needed}} [[Special:Contributions/172.71.158.231|172.71.158.231]] 07:37, 12 November 2022 (UTC) | I've been unable to confirm this so I'm moving it here: A major problem had struck IBM mainframes on and after August 16, 1972 (9999 days before January 1, 2000) that caused magnetic tapes that were supposed to be marked "keep forever" instead be marked "may be recycled now."{{Actual citation needed}} [[Special:Contributions/172.71.158.231|172.71.158.231]] 07:37, 12 November 2022 (UTC) | ||
− | |||
Does the arrow move over time? ... should it? (I think so!) It could be done server side and only regulars would [see, sic] that it changes over time. Then... perhaps we could see different versions of the strip cached on the Internet. --[[Special:Contributions/172.71.166.158|172.71.166.158]] 08:30, 12 November 2022 (UTC) | Does the arrow move over time? ... should it? (I think so!) It could be done server side and only regulars would [see, sic] that it changes over time. Then... perhaps we could see different versions of the strip cached on the Internet. --[[Special:Contributions/172.71.166.158|172.71.166.158]] 08:30, 12 November 2022 (UTC) | ||
Line 32: | Line 28: | ||
:Until somebody starts to audit the issue and asks everyone to poke around and check things... Thenthings get sorted in-situ ''or'' a much needed (YMV!) change of process is swapped in, in the place of old and (possibly) incorrect hacks. [[Special:Contributions/172.69.79.133|172.69.79.133]] 20:00, 12 November 2022 (UTC) | :Until somebody starts to audit the issue and asks everyone to poke around and check things... Thenthings get sorted in-situ ''or'' a much needed (YMV!) change of process is swapped in, in the place of old and (possibly) incorrect hacks. [[Special:Contributions/172.69.79.133|172.69.79.133]] 20:00, 12 November 2022 (UTC) | ||
::Sometimes the "savings" of storing data in a compact form are exceeded by the "cost" of having to convert it between the convenient-to-use form and the compact form. I used to work on a system that used 32-bit words for all data types: characters, shorts, longs. When we started running out of space, we "manually" packed our data, stuffing multiple shorts and bytes into words. But in some cases, the additional code needed to pack/unpack would have taken more space than what we'd have saved in the data, without even looking at the processing time cost. [[User:BunsenH|BunsenH]] ([[User talk:BunsenH|talk]]) 05:52, 13 November 2022 (UTC) | ::Sometimes the "savings" of storing data in a compact form are exceeded by the "cost" of having to convert it between the convenient-to-use form and the compact form. I used to work on a system that used 32-bit words for all data types: characters, shorts, longs. When we started running out of space, we "manually" packed our data, stuffing multiple shorts and bytes into words. But in some cases, the additional code needed to pack/unpack would have taken more space than what we'd have saved in the data, without even looking at the processing time cost. [[User:BunsenH|BunsenH]] ([[User talk:BunsenH|talk]]) 05:52, 13 November 2022 (UTC) | ||
− | |||
− | |||
:The first computerised passport system for the UK had a y2K issue. In fact, it was designed in, because it was supposed to be replaced before 1999. Unfortunately, progress with its replacement was running late. We thought that we could get away with two digits for certain dates because the software was going to be thrown away before the end of 1999. And yes, two digit years were common in COBOL programs because decimal numbers coded using ASCII or EBCDIC were the default for numeric data. [[User:Jeremyp|Jeremyp]] ([[User talk:Jeremyp|talk]]) 15:32, 13 November 2022 (UTC) | :The first computerised passport system for the UK had a y2K issue. In fact, it was designed in, because it was supposed to be replaced before 1999. Unfortunately, progress with its replacement was running late. We thought that we could get away with two digits for certain dates because the software was going to be thrown away before the end of 1999. And yes, two digit years were common in COBOL programs because decimal numbers coded using ASCII or EBCDIC were the default for numeric data. [[User:Jeremyp|Jeremyp]] ([[User talk:Jeremyp|talk]]) 15:32, 13 November 2022 (UTC) | ||
− | |||
− | |||
:1. Having done programming since 1966, I know that much data was stored on 80-character cards (and way before that year and the IBM System/360) and using 2 characters (2.5% of the card) to store the "19" was not acceptable. As processes moved into the tape and disk world, human nature tended to not expand the field to 4 characters (the future is a long way off until, suddenly, it isn't). [[Special:Contributions/172.70.178.65|172.70.178.65]] 07:57, 13 November 2022 (UTC) | :1. Having done programming since 1966, I know that much data was stored on 80-character cards (and way before that year and the IBM System/360) and using 2 characters (2.5% of the card) to store the "19" was not acceptable. As processes moved into the tape and disk world, human nature tended to not expand the field to 4 characters (the future is a long way off until, suddenly, it isn't). [[Special:Contributions/172.70.178.65|172.70.178.65]] 07:57, 13 November 2022 (UTC) | ||
Line 42: | Line 34: | ||
:2. I actually saw a Y2K failure. It occurred at the beginning of 1999 when a job scheduling program scheduled a job for the year 1900 because it was always keeping the schedule active a year in advance. The scheduling software had actually been fixed but the upgraded version had not been installed yet, so there was no significant outage. [[Special:Contributions/172.70.178.64|172.70.178.64]] 08:02, 13 November 2022 (UTC) | :2. I actually saw a Y2K failure. It occurred at the beginning of 1999 when a job scheduling program scheduled a job for the year 1900 because it was always keeping the schedule active a year in advance. The scheduling software had actually been fixed but the upgraded version had not been installed yet, so there was no significant outage. [[Special:Contributions/172.70.178.64|172.70.178.64]] 08:02, 13 November 2022 (UTC) | ||
− | |||
− | |||
− | |||
− |