There are things other than black-on-white and the inverse. I've been using Solarized dark where possible for years, especially in code windows. White-on-black is horrible, but pastel colors on a slate blue-gray background is the most comfortable option for me.
I noticed when I'm working in the morning or generally when it's bright outside, it's sooo much more relaxing with black on white text. With night mode, I'd need to up the brightness way more to be able to comfortably read and type. It was sort of a revelation to me because the "night mode is better" mindset was so engrained into my mind at that point.
One of Apple's biggest innovations imho was to make brightness +/- two of the default keyboard buttons. Every keyboard should replace their F-keys with brightness by default (seriously, who uses F-keys? It's wasted real estate.)
TV's should do this too. With smart TV's/rokus/firesticks/whatever, what's the use of having a channel toggle? Repurpose that for one-button brightness shifts. I don't need my TV being a spotlight into my face when I turn it on to watch a movie at night with the lights dimmed.
Dark mode and red shift are helpful, but really this thread nails it... it's relative contrast that is the big eyestrain contributor. It should be as easy to change brightness as it is volume.
Microsoft copied this with the Surface Book (at least). And in typical Microsoft style, the dedicated brightness buttons control the brightness of the keyboard internal LEDs. Changing Windows' screen brightness is one of the metakeys + del/backspace, not indicated on them.
If the keyboard has media keys, then, generally speaking, F2 and F3 will be linked to brightness by default.
By dumb luck I just found that it's ScrLk and Pause/Break that do brightness controls on my external monitor on os-x.
I wish apple made it as easy to remap these kinds of global shortcut keys as IDE's do.
That’s not even a joke.
I only recently learned about it myself while setting up a new monitor and asking myself wtf is this DDC/CI setting in the menu.
ddccontrol -r 0x10 -w ${NUM}0 dev:/dev/i2c-${DEV_NUM}
The internal: BACKLIGHT_PATH="/sys/class/backlight/intel_backlight/brightness"
sh -c "echo ${NUM} > $BACKLIGHT_PATH"
The numbers are a slightly different scale, so I adjust them in the script.Mainframe programmers.
They are an essential part of interacting with an IBM mainframe (even for basic things like paging up and down through documents).
I'm sorry, what?
I use them all the time. F5 for refreshing all kinds of stuff, or for setting breakpoints in my IDE. F7, F8, F9 for controlling the debugger, other combinations for building/running. F12 for opening developer tools in the browser. Some programs still use F1 for help. F2 in Windows explorer for renaming things. And so on and so forth.
I can't stand keyboards without function keys, or where you have to press Fn to activate them.
The numeric keypad is useful to me too. A bit less than the function keys, perhaps, but when entering a list of numbers it works so much better. What's more: keyboards without numeric keypad also tend not to have the section with ins/del, home/end, pgup/pgdn and arrow keys; instead those keys are often arranged in cumbersome and inconsistent layouts. I use those a lot too.
I don't know in exactly which meaning you use the word "atavism", but I do know that having all these keys available, in a familiar layout, is very very useful to me.
Removing them would break compatibility with an awful lot of things, including Windows itself (which lots of people run using Bootcamp or Parallels). Maybe they're weird, I don't know. Momentum is a powerful force, especially when it comes to software design.
Also for the record, Print Screen takes a screenshot on Windows (and on a lot of Linux systems), which is intuitive and simple. Just because you don't use it doesn't mean it's an abandoned key.
This is one of the reasons I absolutely love my Apple display. It changes brightness automatically and most of the time it does it right.
Also, DDC/CI is a thing and (sometimes) works.
On Windows, I've found Twinkle Tray on the store works reasonably well.
For Linux there's ddcci-dkms on Ubuntu and ddcci-driver-linux-dkms for Arch Linux (on the AUR). They allow configuring the brightness as a regular backlight device. See the Arch Linux Wiki [0].
[0] https://wiki.archlinux.org/index.php/Backlight#External_moni...
[1] https://en.wikipedia.org/wiki/Display_Data_Channel [2] https://github.com/MonitorControl/MonitorControl
Even with brightness adjustments, working in complete dark at night the dark mode is much easier to use. The keyboard lights on the lowest level is a bit too bright in these conditions, white screens are a punch in the face for me.
This is what I like about iOS (and probably every OS has it): after sundown, turn on dark mode.