News for hackers. Stuff that matters.
Re:Technical error with Excel.swapped names.Andreas Babler e... by enjo on Monday June 05, 2023 @01:43PM (#36200036)
Starting in 2003 I spent several years as a principal developer developing mobile office software.

When we launched our excel compatible spreadsheet we diligently formalized every function and wrote tests to verify behavior. It was beautiful.

Then we started receiving lots of bug reports from users because our calculations often didn’t match what they were seeing in Excel. Older Excel versions had lots of bugs and Microsoft had been carrying them forward because at that point it was “better” to carry the errors forward and display results people expected rather than fixing them and having everyone confused by the changed results.

So we copied their behavior as best we could. I wish I had the list still but it was long and full of weird edge cases which caused formulas to be incorrect.

Re:Technical error with Excel.swapped names.Andreas Babler e... by virgulino on Monday June 05, 2023 @02:37PM (#36200960)
Re:Technical error with Excel.swapped names.Andreas Babler e... by lfconsult on Monday June 05, 2023 @01:49PM (#36200123)
Incredible story.
Re:Technical error with Excel.swapped names.Andreas Babler e... by emeril on Monday June 05, 2023 @05:34PM (#36204075)
yeah, that's a classic read
Re:Technical error with Excel.swapped names.Andreas Babler e... by peteradio on Monday June 05, 2023 @04:46PM (#36203353)
How did this work out in the end? I imagine it was difficult to decide whether copying bugs was the correct choice.
Re:Technical error with Excel.swapped names.Andreas Babler e... by enjo on Monday June 05, 2023 @10:54PM (#36207495)
It absolutely was. At the end of the day our product was measured against fidelity to Excel… so any deviance was always bad for us.

I believe Google made the same choice with Google Sheets even.