alexdbird
I'd expand on this: used well, they show the user than a state change is happening directly because of a particular action of theirs, and hint at how they might reverse or modify it.
In fact I'd disagree with masking. If something appeared instantly with no hint as to why, that is a distinct anti-pattern on a touch screen.
You've mangled the steps. You only press one Action icon in this sequence, then you select Print, then you need to select the printer and any other options, then you tap Print. Which of these steps do you think 'abstruse'?
Are you suggesting they should use a little icon of a printer, peripheral that takes many wildly different forms, instead of the word Print?
There are plenty of contenders for 'worst ideas they ever had' and this just isn't up there.
Even in iOS, if you have a hardware keyboard attached! But Ctrl-a/e have come in with BSD, the more common Mac shortcuts are Cmd-left/right, which go to the beginning/end of the current line, whereas Ctrl-a/e follow wrapped text.
And they have F1-12, though you need Fn to use them unless you invert their function in settings. And they have a numerical keypad, as well as pageup/pagedown/home/end/delete - on a full size keyboard. And you can type all those things easily using the meta keys and cursors on the bottom row anyway. And why would screenshot need its own meta key in 2025, with so many ways to screenshot or record. But I digress.
I can empathise, as I always used a full size keyboard on Windows/Linux, and I chose Thinkpads and decent Dells where the extended key layout wasn't completely bastardised.
I insisted on a full size Mac keyboard for nearly a decade afterwards. Then I realised that, barring the niceness of full height cursor keys, it was a useless appendix that meant I had to move my hand ~8 inches more every single time I needed the mouse/trackpad.
Genuine question, what do you think is missing?
I wish it was slightly easier to type a #. But OTOH it's /way/ easier to type accented characters (in either the fast way for regular use or the slow way that's much more discoverable) or different types of punctuation. Without memorising numerical codes, which is what I remember from Windows.
I certainly don't miss all the extra navigation keys, when I have the meta-keys and cursors right under my fingers, exactly the same on any Mac I use.
I'm struggling to remember more than minor differences from a PC keyboard. N.B. I'm in the UK so that might make a difference.
Personally I found the keyboard a breath of fresh air when I switched from Windows/Linux. The whole text editing experience is gloriously consistent and logical, though marred by a growing number of cross-platform apps that don't behave correctly.
What I think of as inane is Linux's having a slightly different key combo for copy depending on what context you're in. Or all the mad extended keyboard keys I used to use that were in a different place on every laptop.
[the keyboard experience is much less well thought out on non-English keyboards though, as another comment points out, come on Apple sort it out]
The things you need from that list are Wheat flour (white), corn flour (starch), Sugar, Cocoa, Baking powder, Salt, Vanilla. I doubt carob adds anything that a spoonful of instant coffee wouldn't.
Now I get your point that it wouldn't produce the same result, but I'd be surprised if it produced a worse result.
It's a nice concept, though the execution isn't perfect. The biggest flaw, which may have been fixed since, is that the power supply decoupling isn't good enough, such that when the batteries get low and the alarm tries to make a noise, the clock detects it as a touch, which instantly snoozes the alarm. We haven't had it since the original batteries though, which were ironically the ones Lexon supplied.
N.B. These are only just big enough to put a glass of water on top, and it might not play well with the touch sensitivity.
But the big flaw in this, especially for saving programming related pages, is that it loses the parts of scrollable content which is not currently in view, e.g. the ends of lines in a code block.