> now will you fix the keyboards for realsies this time?
Hopefully with the quick turnaround more people will bring theirs in and get the failure rate numbers up closer to reality vs. the "small number" of failures they seem to think there is.
My favorite is when autoupdate is done updating, it runs a check to see if anything needs to be updated, and then it reports to me that there's nothing to update.
I recently got a 28" 4K monitor on sale for $250US, and it's almost too big to me, but I love the way fonts look under macOS's scaling. I'm farsighted, so when I wear glasses with a lower resolution, I really don't like seeing the lines between pixels. While not technically "retina", my new monitor is close enough.
Also, I do like working on a 13" laptop -- especially with workspaces. Switching the workspace is almost a complete replacement for the screen real estate of a larger monitor.
Pretty much the same here. FF has always been a battery eater, and even if only one tab is open, it's the sole app in the "Apps using significant energy".
On the magic keyboard, the whole bottom row of keys is shorter than they used to be. Not by a lot, but they're shorter. They're now the same height as the keys above.
>Will a state manager start mediating all application logic now?
The author refers to the shopping cart sample -- which is exactly what I used as a blueprint. I think that's acceptable that the design pattern suggestion is coming from the store layer vs. the template layer (who is focused on the UI/UX).