I think people do think it should fail. Snap isn’t bad, but when people run a command, they expect it to do as asked, or fail. The fact it does something else breaks that intuition, as it’s doing what it thinks you will want instead.
With that being said, it’s not a big deal.
I know most call it AEST, but there are some who call it EST.
I hear timezone names can also be a slight issue at times, some Australians call the eastern time zone EST. Leap years aren’t so bad at times either though. Kind of agree with the rest of it, much of the complexity is from historical dates.
I’d argue not every job will always be 9-5, so you still get people having to explain working hours with non-UTC timezones anyway, whereas all timezone conversions are eliminated if everyone uses UTC.
Huh, I’ve never heard of SoftMaker Office before, good to know it exists. I might check it out.
To add to some of the other comments, I have heard that the issue for LibreOffice is that Microsoft’s own parser isn’t compliant with the OOXML standard that they created. Yet the most important thing is compatibility with Microsoft Office, so you can’t simply build a parser according to the open standard and expect it to work with Microsoft Office. Instead, you need a parser to work the same way as Microsoft’s, which is proprietary. However, admittedly I have never read the OOXML standard or checked MS Office documents for compliance myself.
Therefore, if what I have heard is correct, I would assume that SoftMaker Office has either struck a deal with Microsoft before to improve compatibility, or has simply been better at reverse engineering. Alternatively, what I have heard could be wrong.