> when you design a product to use the internet, you don't really think hard about all kinds of use cases where internet access is deliberately denied
Why wouldn't you, though? That seems like a pretty big oversight. Lazy at best, negligent at worst.
Not everyone in the world has constant internet access, and it seems ridiculous to design an _operating system_ with that assumption.
I like to take an eBook reader to the park, for example. Prior to owning that device, I took a laptop when learning a new programming language. If that laptop had been running BigSur, I'd see all these same issues based on Apple's un-thought-out "design decisions".
It's not like these things fail to work without internet access. Obviously, the vast majority of people using the OS are going to have internet access so assuming actions based on internet access and then failing if you can't connect is accounted for, regardless of the reason (weak connection, no connection, etc). I don't see how anyone can call this behavior an oversight when it works exactly as intended.
Why wouldn't you, though? That seems like a pretty big oversight. Lazy at best, negligent at worst. Not everyone in the world has constant internet access, and it seems ridiculous to design an _operating system_ with that assumption. I like to take an eBook reader to the park, for example. Prior to owning that device, I took a laptop when learning a new programming language. If that laptop had been running BigSur, I'd see all these same issues based on Apple's un-thought-out "design decisions".