> Why should Apple care if a modern Linux kernel boots without workarounds on their hardware?
To sell more hardware?
Obviously I get your point, but there's a bunch of customers who would like good ARM hardware but can't accomplish their work with macOS. It's not like Apple needs this tiny market, but it wouldn't hurt them either.
I've tried to find this for so long. I remember seeing it at the time as a teenager and thinking it was SO COOL. Basically made me discover Apple and want a Mac. :)
I was completely confused when I recently discovered this behavior. I've been using middle-click to open tabs in macOS and Windows for years, and I could not understand why it automatically pasted whatever was in my clipboard.
I think it makes total sense to change the default to be aligned with the other platforms, and leave power-users the choice to keep it enabled if they wish.
I'm a big lover of Kotlin Multiplatform, but I think this is pretty cool anyway. I could imagine making a native Swift library shared between the platforms for memory-sensitive work. I'm not sure about using it to write an app's entire business logic, KMP is going to be more mature for a while for this.
I can easily see a novice user coming from Windows accidentally getting into the edit mode of Plasma and being completely confused. I like KDE as an advanced user but I wouldn't install it on my grandma's laptop.
I agree that it would be great to have it as a first-class citizen in more distros, but I guess the maintenance burden is not negligible. I'm glad Fedora promoted it though.
I assume that Locale.ROOT will stay backwards-compatible, whereas theoretically Locale.US could change. What if it changes its currency in the future, for example, or its date format?
Sure! But my point is there's no one true way to do it and you always have to think about what you're trying to represent and how you're going to use it.
Also, I would argue time manipulation is full of many "edge cases" like this one, which is why it's so hard. It's going to work fine until it doesn't.
Not true. Say you want to save an event that you know will happen on the 14th of July at 15:00 Paris time, in the year 2025. Current time zone rules tells you this will be at 13:00 UTC. Well, if France decides to abolish DST and stick to standard time before then, you'll be wrong.
To sell more hardware?
Obviously I get your point, but there's a bunch of customers who would like good ARM hardware but can't accomplish their work with macOS. It's not like Apple needs this tiny market, but it wouldn't hurt them either.