My favorite is the fact that Microsoft intentionally left a bug in Excel that treats 1900 as a leap year when it wasn’t so they could maintain compatability with Lotus 1-2-3. And at this point fixing it would cause nearly every date value in excel files to display as off by one day and break a bunch of date formulas.
Wow I’ve seen some really weird backwards compatibility issues, but this takes the cake. I would have imagined that in the move to XLSX they could have addressed this and sorted it out when saving, but nope, I guess having all days off by one and maintaining a support page explaining Lotus123 backwards compatibility for forever is earlier?
My favorite is the fact that Microsoft intentionally left a bug in Excel that treats 1900 as a leap year when it wasn’t so they could maintain compatability with Lotus 1-2-3. And at this point fixing it would cause nearly every date value in excel files to display as off by one day and break a bunch of date formulas.
https://learn.microsoft.com/en-us/office/troubleshoot/excel/wrongly-assumes-1900-is-leap-year
Wow I’ve seen some really weird backwards compatibility issues, but this takes the cake. I would have imagined that in the move to XLSX they could have addressed this and sorted it out when saving, but nope, I guess having all days off by one and maintaining a support page explaining Lotus123 backwards compatibility for forever is earlier?