It’s Halloween Week on Unsung, where we’re sharing scary, spooky, and creepy stories.
Everyone knows and hates a blue screen of death, but blue isn’t the only color for the job:
Wikipedia has a list and while it’s very interesting, I think it tries too hard to fit anything into a formula. Can this below really be called a white screen of death?
The most terrifying screens of death might be black, anyway. Even Macs have one:
Earlier PC users would shudder thinking of this black screen of death, which didn’t mean trouble in the moment – it meant trouble forever:
Over at The New Old Thing, Raymond Chen shares a story from the 1990s of the worst case scenario: a black screen of death showing… nothing at all. As always, Chen shares some fascinating technical underpinnings:
If you hold a PC’s power button for 12 seconds, it will turn off at the hardware level without notifying the operating system. This is a safety feature so that you can turn of the computer even if the operating system’s “Shut down” command isn’t working.
After eight seconds of the power button being held down, the Windows kernel realizes that the user is trying to do a force-power-off of the system, and it quickly takes a kernel dump that can be uploaded to the Windows Error Reporting service the next time you turn the system on. […]
These emergency kernel dumps are internally classified as “long power button hold” (LPBH) failures. One of the pieces of information recorded in these emergency kernel dumps is whether the screen consists entirely of black pixels. Those failures are sub-classified as “black screen LPBH”, and they go to a special virtual team for analysis. (I happen to be a member of this black screen LPBH team.)
Sometimes the problem is a broken video driver. Sometimes the video driver is doing just fine, but the desktop compositor is just handing black pixels to the video driver. Sometimes the desktop compositor is doing just fine, but nobody is drawing anything to the screen. And those cases are further subdivided further into cases like “there is nobody around to draw anything” or “the person who normally draws stuff is hung.”
But this time around, this was all… working as intended:
After some questioning, the customer support engineer put the story together: It turned out that this customer really liked the color black, so they decided to set up a goth theme. They set the wallpaper color to black. They set the title bar color to black. They set the button color to black. They set the window background color to black. They set the window text color to black. Every possible color you could pick in the Colors control panel was set to black.
Once you get yourself into this situation, it’s hard to get out because you can’t see anything.
I tried to do this myself in an online emulator, and got pretty far. You can’t really turn everything black, but I can see a setup where it feels that way:
It’s Halloween Week on Unsung, where we’re sharing scary, spooky, and creepy stories. After this and this, the post below feels like a third story in an accidental “angry rectangle” trilogy.
If you used Windows in the 1990s or 2000s, it’s likely you’ve seen this effect, which today we’d call a “glitch”:
The reason for it had to do with window compositing.
If you look at how things are drawn on screens, at some point you realize that despite all the handwringing about additive vs. subtractive colors, on-screen drawing is not really that far off from an artist working on a painting: in both cases you can’t really remove anything, but you can always add new paint. On screens, at least, the paint is 0% thin and 100% free, so nothing prevents you from forever piling it on, but ultimately it’s the same end result: removing a window from the screen isn’t really deleting its pixels, but painting over it with pixels of the background, or another window, or the memory of what was on screen before the window appeared.
It’s the job of compositors to abstract that uncomfortable truth from you, but Windows 9x and XP compositors weren’t nearly as advanced as modern ones. If the underlying app crashed (which explains how most common examples of the above are of the “this application is not responding” variety), the system would end up skipping the erasing-by-drawing step, and compositing directly on top of the previous drawing. It wasn’t a problem if the window was stationary. If you moved it, though? Window ghost trails.
Compositors have improved since those years, yet you can still occasionally see this very problem rearing its fascinating-looking head. But it is more likely you will see its more modern equivalent, having to do with video compression.
Common video compression doesn’t treat all the frames equally. Instead, to save on space and bandwidth, it encodes occasional frames as “I frames” – those are complete sets of pixels from top left to bottom right – and all the other frames a “P frames” – containing, instead, the movement of the pixels drawn previously. Movement is cheaper to encode, in part because on many frames or parts of frames, in any video, there is no movement at all.
I frames are perfectly deterministic, but P frames are more like dead reckoning, as they rely on the previous I frame and all the preceding P frames being there for a perfect result.
In ideal conditions, you will never notice different types of frames and the video will feel as smooth and fluid as real life. But if some P frames happen to be skipped or – especially – if an I frame is skipped, you will see a strange but recognizable visual effect, as the movement of one group of pixels is applied to the wrong group of pixels, and then everything snaps back to reality as the next I frame arrives:
As we’ve seen with other things earlier this week, this category of glitches have been co-opted by digital artists, who named this effect datamoshing, used it creatively in places like music videos – here’s a video for a band Charlift…
…and started repurposing it in other places, too. This video by Jam2go has a nice visual summary of everything I wrote above, and then follows that by trying to recreate the effect in a videogame engine, and then even in more “analogue” settings:
Whatever you now find weird, ugly, uncomfortable and nasty about a new medium will surely become its signature. CD distortion, the jitterness of digital video, the crap sound of 8-bit – all these will be cherished and emulated as soon as they can be avoided.
The Windows background glitch has been remade many times in recent years, too, for example by Jez Corden in 2023. Corden wrote about it, and his recreation is so fun to play around with today, freed from the terror of seeing your app crash and your work potentially lost.
But the glitch was used creatively even when it was still around – and I bet you will recognize this, as it’s one of the most well-known visuals of the Windows 3.x era:
Yes, this is the famous Windows Solitaire, written by Wes Cherry, who combined not clearing the background with some simple physics for an iconic effect. From one of the fans:
I used to watch the whole thing just waiting for the perfect bounce: leftbound from the rightmost stack, with solid black edge. ¶ It’d practically just be gliding along the floor by the time it reached the edge of the screen. Beautiful.
I like these categories of work, the “creatively embracing a glitch” projects, the “intentionally recreating bugs in environments that no longer have them, for aesthetic or artistic reasons” ideas, and the “remixing a glitch in a medium where it doesn’t even make sense” efforts.
Because of course the Solitaire effect has been remade as well – by Mr Doob in 2012, and I imagine by countless others – but it went even further than that:
It’s Halloween Week on Unsung, where we’re sharing scary, spooky, and creepy stories.
Imagine this: It’s 8pm on a rainy Sunday night in the ’90s, and you’re bored, so you boot up the family computer looking for something to do.
But you’ve already played Solitaire a bunch, and you still don’t really get how Minesweeper works. You’ve had a laugh in paint, making abstract art. So now what?
Keep in mind, you’re not allowed to go onto the internet because firstly, someone in the house is already on phone call and secondly you’ve already been warned about running up the phone bill, but then you remember something a legend that had been circling around the net about a secret portal into a demonic realm.
And the way to get there, so they say, was through Excel.
I’m just going to leave it at that. For the rest, watch the video:
Over the years, I learned about many gotchas and strange differences between keyboard handling on Mac and Windows – pertinent especially to web apps, which use the same codebase to cater to both. I thought it might be helpful to someone if I compile them all in one place.
This post is meant to be a reference, and there aren’t any cute or riveting stories hiding inside – if this seems boring to you, feel free to skip to the next one!
Different names for keys
What Windows calls Backspace, Mac calls Delete. What Windows calls Delete, Macs call Forward Delete. (This means saying “Delete” without specifying the platform might actually be confusing.)
What Windows calls ⏎ Enter, Mac calls ⏎ Return. However, Macs also have an ⌤ Enter, although only on a numeric keypad (previously, it was even there on laptops!). On keyboards without the physical Enter key, you can simulate it via Fn+Return.
In most Mac software, Enter and Return do the same thing. There are a few exceptions – for example, Photoshop adds a new line on Return but commits on Enter, and some classic pro apps like Cubase or Pro Tools do different things, too – but it seems to be a dying tradition. (If you are curious about the history of Return and Enter, I wrote about it once.)
Windows customarily calls the secondary key Numpad Enter. I don’t believe Fn+Enter works to simulate it.
Generally, third-party keyboards use Windows verbiage – so, Backspace and Enter. If a keyboard offers Mac conventions at all, they usually only extend to modifier keys.
Modifier keys
⌃ Control on Windows is the equivalent to ⌘ Command on a Mac. (Paste, for example, is ⌃V on Windows and ⌘V on a Mac.) But, confusingly, Apple devices still have a Control key, too. This was originally meant for terminal applications, but these days many GUI apps use it as an extra modifier key of much lesser significance than Control on Windows.
This means that for apps, Windows devices offer Ctrl, Alt, and Shift – and Macs offer ⌘ Command, ⌥ Option, ⌃ Control, and ⇧ Shift. That’s one more modifier key, and thus more space to breathe. (We’re not counting the Windows key or the 🌐 Globe/Fn key since those are technically reserved by the operating system.)
Some keyboards offer extra key caps you can swap to match the platform, for example:
Others cover all the bases on fixed key caps, in an awkward way:
Many stick with Windows-only legends.
(Just swapping the key caps is not enough. The keyboard also has to swap the scan codes it sends, since the code for Alt is the same as the code for ⌥, and the code for ⌘ is the same as the code for ⊞.)
Words vs. symbols
Apple devices rely more on symbols on their keys and in their menus, although they don’t do so consistently. Here are all of them:
⇧ Shift
⌃ Control
⌥ Option
⌘ Command
⏎ Return
⌤ Enter
🌐 Globe/Fn
⇥ Tab
⎋ Esc (not printed on keyboards, for some reason)
⌫ Delete
⌦ Forward Delete
⌧ Clear
≣ Contextual Menu (only on full-size keyboards)
⇞ Page Up (only on full-size keyboards)
⇟ Page Down (only on full-size keyboards)
↖ Home (only on full-size keyboards)
↘ End (only on full-size keyboards)
Actually, I lied about the last four. On modern Apple keyboards, they are:
↑ Page Up
↓ Page Down
⤒ Home
⤓ End
Reusing the regular arrows for Page Up and Down is one of a few perplexing decisions from Apple’s keyboard designers. The arrow key symbols look like this – ◀▶▲▼ – but only on Apple keyboards. Here is an older and a newer Apple keyboard showing what happened:
(Luckily, the confusing dual arrow key situation only happens on less popular, full-size keyboards.)
Historically, Apple keyboards used symbols more on non-US keyboards, but starting with the 2026 models, they unified when they show symbols and when they show symbols and legends, across all keyboards. (The only key with just a text legend is Esc, making the appearance of ⎋ in menus extra puzzling.)
Windows keyboards typically use words – this is why in tight quarters you sometimes see shortenings like Ctrl, Bkspc, PrtSc, Del, PgUp, Win, and so on. (I don’t think Apple ever abbreviates their legends with the exception of Esc for Escape.) In some countries, the legends are translated – as an example, in Germany, Ctrl sometimes appears as Strg.
The symbols that crossed over to Windows side are:
⇧ for Shift
⇪ or 🔒 or a similar symbol for Caps Lock (on non-US keyboards)
⏎ for Enter – note the same arrow as Mac’s ⏎ Return
← for Backspace – note a different arrow than Mac’s ⌫ Delete
⇥ for Tab (you can also sometimes see ⭾, which is a symbol representing Tab and Reverse Tab together; Reverse Tab used to be a separate key on some 1970s terminals)
⊞ for Windows key – the style of the logo will be different depending on the age of the keyboard, roughly matching the Windows logo at the time; some keyboards also use a more abstract shape, or call the key Start or System instead of Windows
≣ for contextual menu key (a.k.a. Application Key) – just as Apple added that key on its large keyboards, Microsoft started removing it in favor of emoji key, Office key, and then Copilot key
⌃ for Control (especially in nerdy contexts)
I have not seen any other popular symbols on the Windows side of the aisle, and I am not even sure if the above would be widely understood. But here’s an example:
Here is the same Chrome menu on Windows and on macOS:
(In other words, you’d never say “⌃V is Paste on Windows” like I did above.)
Function keys
Both Windows and Macs have function keys.
On Windows, traditionally those were claimed by the operating system or the apps as shortcuts. Here are some examples of well-known function key assignments:
Alt+F4 – close the app
F1 – help
F11 – maximize window
F12 – dev tools in browsers
On Macs, traditionally the apps didn’t reach for function keys, as those were reserved solely for the users to do stuff with. (However, some combination of ⌃ and function keys are used by the operating system for accessibility options, and I occasionally see apps use function keys these days.)
Windows keyboards top off at F12, but some Mac keyboards reuse the three special PC keys, and even take over the unnecessary Num Lock/Caps Lock/Scroll Lock island, and end up going up to F19:
Access to extra characters
In text fields, Apple has a system where pressing ⌥ with printing keys outputs more characters, for example ⌥Q outputs œ, and ⌥7 outputs a ¶ pilcrow. Additionally, ⇧ works in this context, so for example ⌥⇧Q outputs Œ, and ⌥⇧7 outputs a ‡ double dagger.
Note that not only letters, but basically all printing keys have secret ⌥ and ⌥⇧ assignments. (Also note some of these are dead keys.)
Also, ⌥ assignments vary per location! The above was U.S. English, here’s Polish with a lot of differences:
This means it’s best to avoid ⌥-based shortcuts in text fields, since they might conflict with some important character.
By the way, while the above two are just mock-ups, on some physical keyboards (here: British English), some of the important ⌥ invocations are actually printed on keys:
Windows doesn’t have the above feature. However, Windows has an alternative feature where typing Alt+numpad keys allows to enter any character by its code. (For example, Alt+0128 outputs €. Num Lock has to be enabled. I don’t think it’s possible to do it without a numeric keypad present.)
Mac has a version of this feature, but it requires adding Unicode Hex Input keyboard and switching to it beforehand. Then, pressing ⌥20AC outputs €.
Right Alt key on Windows
While Mac modifier keys are completely symmetrical, Windows makes an exception for Alt. On many non-US keyboards, right Alt is also known as AltGr, and does something similar to ⌥ on a Mac: it outputs letters when pressed in combination with printing keys.
For example, on Polish keyboards AltGr+A = ą, AltGr+C = ć, AltGr+Shift+A = Ą, and so on with 15 more combinations. Many other keyboards do similar things.
The way it differs from ⌥ on a Mac is that these are usually reserved for core letters and punctuation necessary for each language, rather than the typographical smorgasbord that Apple provides.
For legacy reasons, and also for keyboards that do not have a physical AltGr key, you can also invoke all these using Ctrl+Alt combinations instead (so, Ctrl+Alt+A = ą). This means that just as you have to be careful about ⌥-based shortcuts in text fields on a Mac, so you should be of Ctrl+Alt-based shortcuts on Windows.
Just like on Macs, on some keyboards, selected AltGr options will be printed in the corners or fronts of keys:
Text fields
Text fields in Mac OS apps and web browsers/websites use some of the standard Unix/Linux shortcuts based on the ⌃ Control key:
⌃A – move to the beginning of the line
⌃E – move to the end of the line
⌃F – move to the right, or forwards (hold ⌥ to jump through words)
⌃B – move to the left, or backwards (hold ⌥ to jump through words)
⌃N – move down or to the next command
⌃P – move up or to the previous command
⌃L – scroll the window so that the text cursor is in the vertical middle
⌃H – delete (backspace)
⌃D – forward delete
⌃K – delete (kill) to the end of the line
⌃T – swap (transpose) the adjacent characters
⌃O – insert new line, but (contrary to Return) do not move the cursor there
You can combine many of the above with holding ⇧ to extend the selection.
A small group of vocal users love these.
Windows still supports Shift+Delete for cut, Ctrl+Insert for copy, and Shift+Insert for paste. I am not sure how many people use these.
On a Mac, in simple input fields, ↑ and ↓ jumps to the beginning and end (same as ⌘←→). This often conflicts with command line history, autocomplete pop-ups, and so on.
Windows doesn’t have this convention, and Home and End serve this purpose instead.
Macs support the iPhone-inspired convention of holding a key to show related accented characters, instead of triggering auto-repeat. Windows doesn’t have this feature.
Differing shortcut conventions worth knowing about
On a Mac, redo is typically ⌘⇧Z. On Windows, it’s typically Ctrl+Y.
On a Mac, refresh (in browsers, etc.) is typically ⌘R. On Windows, it’s typically F5, although browsers support Ctrl+R, too, and seem to be shifting to that being the default.
Reserved keys
Windows’s eponymous ⊞ Windows key is reserved solely for the use of the operating system, and so is Mac’s 🌐 Fn/Globe key. (Although I am not 100% sure of that as I found one place you can create 🌐 shortcuts as a user – I’m just not certain if it’s intentional.)
However, each platform also has a lot of shortcut combinations that are effectively unavailable, for example ⌘⇥ and ⌘M on a Mac, or Alt+Tab and Ctrl+Shift+Escape on Windows.
If you’re a web app, you will compete for shortcuts with the operating system (like any app would), but also with the browser itself. You can typically take over shortcuts like ⌘S or ⌘P, but depending on the browser or the platform, some might be sacred and unavailable. No Mac browser will allow a website to claim ⌘Q, ⌘W, or ⌘T. Safari won’t allow a web app to override ⌘R. Arc browser won’t allow to override ⌘⇧C. (This is not a complete list.)
Jumping around
Tabbing and Shift tabbing is customarily used to jump between UI elements, but it behaves slightly differently in native apps.
On Windows, tabbing jumps through all interactive elements:
On Mac, Tab jumps only to those interactive elements that require keyboard to operate (such as input fields). You can toggle a System Settings preference and ask macOS to mimic Windows behaviour – see the last toggle below – but it’s not supported well everywhere.
PgUp and PgDn work differently:
On Windows, they move the text cursor a screen up or down.
On a Mac, they scroll the view up and down, but they do not move the text cursor if it’s present (so, they are more an equivalent of clicking on the scrollbar chute).
Similarly, Home and End work differently:
On Windows, they scroll the contents (and move the cursor if present) to the top or the bottom of a view, or move the cursor to the beginning or the end of an input field.
On a Mac, in views they scroll to the beginning or end without moving the cursor. In input fields, Home/End do nothing, but you can use ⌘←→ to accomplish the same.
On both platforms, Fn+↑↓ does PgUp/PgDn, and Fn+←→ does Home/End. (Do you see how confusing it is to say that given that ↑↓ already mean PgUp/Dn on a Mac?)
Windows has a tradition of enabling access to menus and visible controls by pressing Alt and letter keys. This has evolved over time and is not as consistent as it used to be, but it might be worth knowing about.
Less popular keys
On a 100-plus-key keyboard, Windows might have:
Insert – still used in some contexts for overtyping
In a strange twist of fate, it’s not only third-party keyboards that favor Windows legends. Some of Apple’s keyboards in between 1980s and 2000s showed PC legends, too! (This was to court PC compatibility of then-beleaguered Macs.) Here’s the classic Apple Extended Keyboard, showing legends for Insert, Delete (naming it Del to avoid confusion with its own), Print Screen, Scroll Lock, Pause, Num Lock, and Alt:
Did I miss anything or make a mistake? Let me know!
Dragging and dropping files with your mouse in the Finder is nice, but there are many moments you wanna reach for the keyboard instead. Finder supports that. You dragged the file to a wrong place by accident? ⌘Z can undo it in a jiffy. You already have the right windows open? ⌘C and ⌘V can start a copy faster than the fastest of mouse gestures. And for cutting, there’s always…
…well, no, there isn’t. To the best of my knowledge, the Cut item in the menu never lights up around files or folders; you simply cannot ⌘X or cut in the Finder.
I think I understand the reasoning here. Of the Fantastic Four that is ⌘ZXCV, it’s ⌘X that is the truly dangerous one. Putting something in a clipboard is always a balancing act – a moment of inattention, and ⌘X turns into Delete. We generally accept it for text because the stakes are not very high, and text undo is basically too cheap to meter. Even then, occasionally, disaster strikes.
For files, the stakes are quite a bit higher. The creators of the File Explorer in Windows knew all that – yet, Cut still works there:
The way this is done is that the file isn’t immediately removed and put on the clipboard. No, only the intention of cut is registered – one half of the handshake, if you will – but the file stays put and nothing happens until the deal gets closed via a subsequent paste.
Or, almost nothing. There is a signal that ⌘X took effect – the cut files turn slightly transparent to indicate they put on their shoes and they’re ready to go. But if you don’t finish the paste, they become solid again the moment you cut something else, or when you restart the computer. (I wouldn’t be surprised if there’s a timeout, too, although I couldn’t verify that.)
I am not sure why macOS doesn’t do it the same way, particularly since they have a half-finished state designed already, for copying larger selections:
This feels like a strange omission I don’t fully understand, particularly given that it was vintage Mac OS that put the ⌘XCV combination on the map:
What’s even stranger is that the Finder has a command to move files – but an unusual one, buried inside the secret area in one of the menus, as an ⌥ alt to Paste:
It works. By putting the action on the other side, it avoids the “file floating in outer space” challenge, too. But it’s so undiscoverable that even though Move Item Here was introduced in 2011, I only learned about it a month ago as I started researching this more – and even though I know about it now, it still feels profoundly alien, being on the wrong side of the cut/paste continental divide.
In a reversal of typical state of things, it feels to me is that it was Mac that did a simple/cheap thing, and Windows that spent extra effort to dress it up into clothes of an existing Cut for reasons of familiarity, consistency, and better experience. Sure, a keyboard way to move files like Move Item Here is somewhat valuable, but nowhere near as valuable as a traditional cut, put under ⌘X ahead of ⌘V, working the same as everywhere else for years, even for decades, as one of the first denizens of motor memories all around the world.
From Marton Barcza at TechAltar, a good 12-minute video analyzing what went wrong with the famed Live Tiles that Microsoft was pushing throughout most of the 2010s:
Now, among Windows Phone fans the pervasive opinion is that Live Tiles have failed because Microsoft did a poor job with them, which I think is at least partially true – after all, even many key Microsoft apps like Skype had broken Live Tiles half the time, the Windows 10 start menu was filled by Microsoft with Live Tiles that were clearly just animated ads rather than showing you something actually useful, and the company of course never built out any of their advanced interactive concepts either.
But while all of that might be true, the fact that every major company has walked away from this idea and nobody else has picked it up since, means that there probably are more fundamental problems with this idea. And I can think of three distinct ones:
user experience,
form factors,
and horizontal integration.
Barcza goes on to talk about some specific interactions and problems, and arrives at the conclusion that Live Tiles ended up at this unpleasant intersection where they’re tried to be icons, widgets, and notifications all at once, not doing a particularly great job at either task. That, and there were also challenges with the design primarily being mobile-first, and struggling surviving a jump to a large screen. (Live Tiles were abandoned in 2017, at which point desktop Windows reverted back to what it was before, and the mobile/tablet lines were altogether disbanded.)
What I found interesting in watching this today is that it feels Apple has made some similar mistakes in their Liquid Glass approach and wider platform unification desires (see: macOS Settings). Both these and Live Tiles attempted to create A System Of Systems, and both ended up occasionally feeling like they awkwardly crowbarred some wider concepts into places where they didn’t truly belong.
If it helps with your further research, I understand Live Tiles were part of a bigger UI effort called Metro and started in earnest with Windows Phone.
For decades now, Raymond Chen has been posting to his blog The Old New Thing about various technical Microsoft quirks, occasionally venturing into Unsung territory. Last week, Chen shared a nice remembrance of Tony Krueger, a person responsible for implementing the red squiggly underlines in Word:
Tony worked on Word 1.0, 1.1, 2.0, then on Word for OS/2 and Word for Mac, then returned to Word 6.0 and several versions beyond that. He probably holds the record for “most versions of Word shipped.” […]
Tony made the spell checker much more unobtrusive so that it didn’t interfere with your foreground work. And when it found a problem, instead of waiting for you to trigger a spell check, it immediately drew red squiggles under potentially-misspelled words (and later green squiggles under potential grammatical errors). […]
Today, there are red (and even green and blue) squiggles in nearly every word processor, and often outside word processors. Tony did it first. The next time a red squiggle catches one of your mistakes, say thanks to Tony. I think he’d appreciate it.
Read on for some fun celebrity encounters, and even a touching comment from Krueger’s father. Another person adds that a “PM named Diana” and another Microsoft employee, Jim Walsh, might have been the people who designed the feature.
Chen doesn’t name it specifically, but it’s my understanding that the red underlines were named Spell It (meh), and appeared in Office 95 in 1995. Steven Sinofsky confirms it on his blog, adding “The red squiggles were simply reflective of a proofreader’s style of mark (also one of the early uses of color in the interface).”
As far as I can tell by looking at various screenshots and photos of boxes, the feature wasn’t advertised at all. It was only mentioned more explicitly a few years later in Office 97:
When taking screenshots, macOS at some point followed iOS and introduced a “floating thumbnail,” which serves as a proxy of the screenshot you just took – you can drag it somewhere, open it to annotate, etc.
The thumbnail is a nice gesture. The problem is that I rarely do the things it enables, so the thumbnail is now an extra thing to deal with and dismiss. And you have to dismiss it, because inexplicably on macOS the floating thumbnail is diegetic, meaning it itself can be screenshotted. And this happens, routinely, if you do a few screenshots quickly in a row – the screenshotting tool literally ruining your screenshots. “You had one job,” &c.
(“Diegetic” is perhaps my favourite pretentious word. It generally stands for “in-universe.” If characters in a movie are listening to the song, that song is diegetic. If the song is just for the viewer as part of the soundtrack, that song is non-diegetic.)
You can turn off the thumbnail, but then outside of the sound – which is unreliable for other reasons – there is nothing else to tell you the screenshot was taken. And I think it’s good to have some sort of a confirmation, especially since the screenshot shortcuts are so harrowing.
Now, on Windows, when you press the equivalent (Windows key + PrtSc key), this happens:
I think this is better. It’s elegant, unmistakably recognizable as a screenshot, gone immediately, and a cute skeuomorphic nod towards old cameras.
As a Mac user I naturally focus on that platform, but Windows 11 has had its own share of problems – and that list has grown so vast it’s hard to know where to start.
So let’s pick it up at random, with a post by Thom Holwerda with a great title “You can actually stop Windows Explorer from flashbanging you in dark mode”:
One of the most annoying things I encountered while trying out Windows 11 a few months ago was the utterly broken dark mode; broken since its inception nine years ago, but finally getting some fixes. One of the smaller but downright disturbing issues with dark mode on Windows 11 is that when Explorer is in dark mode, it will flash bright white whenever you open a new window or a new tab. It’s like the operating system is throwing flashbangs at you every time you need to do some file management.
I find the videogame-inspired nickname darkly – I’m sorry! – funny, but the problem is real. It looks like this (video via windowscentral.com):
It’s not a problem unique to Windows 11 – just the other night I saw this on Wikipedia on my iPhone, exacerbated by the delayed reaction of Liquid Glass buttons spastically adapting to the changing background:
But there is something about this that feels a notch more important than other visual and layout issues.
I think this is because dark mode is a contract – we’ll lower the brightness, and we’ll let your eyes rest. There’s a physiological part to it: a sudden flash of light when your eyes are not expecting to it can be actually physically painful. I think it’s worth thinking about it and futureproofing and sanding dark-mode views especially at their edges: loading states, error messages, signing in and logging off areas. The “flashbang” analogy is very apt, and especially so on bigger screens.
83% of participants associated the floppy disk icon with saving. […] Another 13% described this object literally with responses such as “disk,” “disc,” or “this is an SD card for storing information.” These responses were not coded as “save,” but still suggest familiarity with the image.
What a fascinating journey! The icon didn’t change at all, but its perception went from being a literal representation of a familiar object, to a skeuomorph once floppies were replaced by hard drives, to then a symbolic representation of physical media in general (a lot of people think it’s an SD card – or perhaps even that floppy disks and SD cards are one and the same), to increasingly just an abstract symbol that represents saving as a concept, registering similarly to the circular arrows for syncing, and an arrow pointing south for downloading.
NN/Group is itself kind of a floppy disk, trying to walk a fine line between their legacy and reinventing themselves. They’re dismissed by many as old-school, academic, boring enterprise software aficionados, relics of a different era. I see some of that and often disagree with them, but I also sometimes appreciate their rigor, reliance on user studies, and outright dismissal of fashion in UI design. I want to revisit their site in more detail and see how I feel about it today, 30 years after Jakob Nielsen’s books rocked my world.
It taught me many things and it clarified that things were more complicated than they seemed. Windows Vista (widely seen as failure) perhaps wasn’t so bad, and 7 (quoted by many as the best Windows ever) was not that far away from Vista, down to its internal version number being 6.1 to Vista’s 6.0.
It’s also interesting to reflect on this today, when macOS is having its own Vista moment.
There is also a follow-up video on Windows 8, the possibly most consequential Windows release of that era, with product decisions that reverberate still today.
Main takeaway: An entire book could be written and a lifetime of lessons learned from Microsoft’s “.1” releases.
One thing I really admired in earlier versions of Windows was the thing that was also its weak point: the keyboard orientation.
I miss the old tradition in Windows where many commands had underlined letters, and you could simply press Alt and that letter to jump to it:
If I remember correctly, eventually this got simplified so that the underlines were only there when you held Alt (although I bet there was an option to keep showing it all the time).
Opening Windows 11 today, it feels like the system got less elegant. I can still press Alt and stuff happens, but it doesn’t look nearly as good or tightly integrated, and the two alternate entry points (Alt and the keyboard shortcuts) become muddled:
In the meantime, on a Mac, in various places apps reinvent the wheel by their own thing.
I just saw this in Nova, the code editor, which is very thoughtful; those shortcuts only exist within this dialog (and one wonders if they couldn’t just be letters without modifiers)?
A little more old-fashioned from Photoshop, and the same question: could they just not be digits, without requiring ⌥?
Previously, I mentioned yet another idea from DevonThink.
I appreciate these gestures toward moving faster via a keyboard, but I wonder if we lost something that already used to work well in old Windows.
Every so often, a wonderful thing happens: someone young enough to have missed out on using computers in the early 1990s is introduced to the Windows 3.1 “Hot Dog Stand” color scheme.
I can’t figure out whether Gruber’s take (“That’s Microsoft.”) is also a subtle jab at Apple in the year of Liquid Glass.
Also, great first comment under the original post:
I assume “Plasma Power Saver” served an actual purpose - it was intended for users of “portable” machines having a gas plasma display. Early ones were monochrome (orange) and I guess the actual color hue didn’t matter so much as the intensity.