erAck

> The link is just about a move from one part of Munich to another (MS German HQ has always been in Munich).

Nope. They moved from Unterschleißheim (administrative district of Munich in Upper Bavaria) to Schwabing (district of Munich town), which tax-paying wise makes the difference.

And actually it depends on the locale you work in whether SEPT is a valid month abbreviation or not.

SEPT-2 is changed to date (that is how all major spreadsheet software works if an input is accepted as date), SEPT2 is kept as text as entered.

> if they had a "scientific mode" to not be smart with your data

That "scientific mode" is called text. Assign the column type Text during CSV import and nothing is converted to numeric or date.

LibreOffice Calc: "SEPT-2" is a date, "SEPT2" is not.

So we need 4400 persons falling off a roof to be par with nuclear power plants. I still consider this ratio a much better outcome than a power plant going off anywhere near (radius to be defined in Mm depending on wind direction).

With the difference that one person dropping dead from a roof hurts one family, a nuclear plant going off spoils a huge area for generations.

Whether solar and wind power are major energy sources depends on where in what region you live.

Lovely. Thanks!

Try to "simply follow" when it's nested twelve levels deep.

Anyhow, with both approaches, nested or early return, the reader has to read the function from the beginning (or read back until the relevant part) to grasp when exactly a code portion will be executed. In both cases, all if's are relevant, there's no guessing.

Regarding your fraction example there:

=RAWSUBTRACT(0.1,-0.2,1/3) => -0.033333333333333

=RAWSUBTRACT(0.1,-0.2,2/7) => 0.014285714285714

So which one is closer to 0.3?

As you referenced that bug and there also gave an example involving fractions and =0.1+0.2 you would certainly also agree that the binary floating point representation of =0.1+0.2-0.3 is not 0.0, still Excel displays 0 as result (and so does Calc) instead of 5.551115123125783E-17 because users expect that.

Your bit-level accuracy approach isn't as simple when it comes to user experience and Excel compatibility.

Exactly. You don't want documentation editors having to learn git and all cumbersome processes first. They may not even want to learn that. They want to edit and get their changes in.

If it's Electron it's the reason to not use it.