Excel geht fälschlicherweise davon aus, dass das Jahr 1900 ein Schaltjahr ist | „Obwohl es technisch möglich ist, dieses Verhalten zu korrigieren, überwiegen die Nachteile die Vorteile.“

    https://learn.microsoft.com/en-us/troubleshoot/microsoft-365-apps/excel/wrongly-assumes-1900-is-leap-year

    Share.

    25 Kommentare

    1. Well I finally learned something in Reddit. I also thought 1900 was leap, but it is not. The OP is correct.

    2. Greedy_Sneak on

      For anyone wondering, years divisible by 100 must also be divisible by 400 to be a leap year. It’s to make up for the bit of calendar drift that regular leap years dont.

    3. Tall_Midnight_7240 on

      How can this happen… like it’s not obviously.. to fix it would break something? What … lol 😂 it’s comical

    4. To be clear, this isn’t a bug in Excel; it was designed to do that.

      It *was* a bug in Lotus 1-2-3, which was the second major spreadsheet program (after Apple’s VisiCalc and before Excel). Excel intentionally reproduced that behavior so it would be easier for businesses to switch from Lotus to Excel.

      This is fairly well-known tech lore, but it’s also explained in the article.

    5. pleachchapel on

      This buries the lede: this error wasn’t made by the Excel team, it was made by the Lotus team & deliberately preserved when creating OG Excel for migration compatibility.

      Way more stuff in our world is held together with duct tape & bubblegum than most people realize.

    6. cazzipropri on

      yup.

      welcome to microsoft.

      Its code is FULL of well known bugs that CANNOT be fixed, *because too much code has been written to work around them*.

      UPDATED: added explanation in italics.

    7. >the disadvantages of doing so outweigh the advantages

      Until we get to 2100 and everything breaks

    8. occasional_engineer on

      People have pointed out why this is (Lotus 1-2-3 compatibility), but it’s also good/fun to remember that datetime in computing is just….difficult. Not because of the concept, but because there are so many quirks in our datetime system that just build up. We have leap days, leap seconds, calendar changes, daylight saving time, timezones etc And lots of them have occurred a bit randomly over the years so whoever programs in your datetime conversions needs to take into account all the changes over the years.

    9. rumforbreakfast on

      Lots of schoolyard defences going on in this article.

      “He did it first, miss!”

      “An older boy made me to do it”

    10. Honestly, you shall not mess with excel. This is the cornerstone of the global financial system.

    11. In the 5th grade I told my class that Feb 29, 2000 happens once every 400 years and everyone laughed at me, and the teacher said I was wrong and I tried to explain but no one listened. Smh 

    12. An early blogger, Joel Spolsky, wrote about this exact issue in his blog [My First BillG Review](https://www.joelonsoftware.com/2006/06/16/my-first-billg-review/). In it he described when he wrote the Excel Basic spec, he stumbled upon this error, and then went to an old Excel developer who enlightened him to the Lotus 123 issue. Finally, when Bill Gates interrogated him about his spec, he was able to respond to Bill’s hardest question with this arcane tidbit.

    13. No_Cat_No_Cradle on

      but has Microsoft considered how funny it would be if they made a technically correct change that pissed off their entire user base by shifting every date by 1 day?

    14. t3hmuffnman9000 on

      Of course it stems from Lotus Notes. God, that was such a dumpster fire program.

      So glad I don’t have to support that crap at work anymore… <shudder>

    15. AirborneSysadmin on

      Fun fact:  There are a number if popular systems out there including classic Macs, Igor and Labview that use a Jan 1, 1904 epoch specifically because they didn’t feel like dealing with the 100 year leap year rule.  

    Leave A Reply