The Y2K issue (I was very much involved then) was much more to do with the inability of equipment makers to prove Y2K compliance to their
usually much bigger customers (whose "compliance managers" aggressively demand compliance certification "or else") than the equipment having an actual issue.
In the vast majority of cases the equipment didn't even have any kind of date processing. No more than your washing machine has.
So this can and will repeat itself just the same.
And, after say 10 years, how many companies will be able to find the sources, let alone find somebody who can read them (coders generally hate reading somebody else's code
) let alone be able to find somebody who can fix it.
In most cases the project won't even compile after say 10 years after it was finished. Or 5 years. Most people know they should archive sources but few know they also need to archive the tools. Maybe create a VM when a project is "finished" and then you can archive the VM - it is only about 10GB. But nobody does this. I had a taste of this with FPGA projects (I used to do FPGA / ASIC design work, using Xilinx FPGAs, and their newer tools could not load older sources. The tools could not be archived either because they were dongled
In the end, even though I had the dongles cracked, I got out of it; it became a completely ridiculous business, if you were running your own company and had to think long term.
Project archival is a big issue in many relatively critical areas. For example when Bendix King was taken over and (as usual) trashed by Honeywell, anybody who could write Hello World left to Garmin, and products (e.g. autopilots) finished in say 1999 were completely dead in 2003. The sources "exist" somewhere (I am told by an ex insider) but nobody could touch them.