Often using software without white mode the thing is so bright, that the walls near me get lighted up as if I was using a flashlight or something.
Thus I have to make the screen less bright, but often this also make the screen colors and contrast get all screwy and I still can't see anything.
I miss Win 9x era grey interface... it wasn't beautiful but I could actually see stuff.
Not everyone is.
That's pretty much the issue here in a nutshell.
When I play games I get the vivid colors and contrast so all good.
It's just that monitors nowadays don't even default to SRGB profile.
Windows in hdr mode with hdr monitor(vesa certified) and windows in sdr with a monitor set to srgb mode should have an almost identical visual.
(I tried searching a few times, no luck..)
The default UI here on HN features your username in #828282 on a background of #F6F6EF [1], a contrast ratio of 3.54:1. The up and downvote arrows are #999999 on #F6F6EF [2], a ratio of 2.62:1. On a high-brightness screen, these less-intense contrasts look great. And this is far from the only place with 'nice calm greys' that are intentionally used by designers to reduce eye strain.
I run Visual Studio in dark mode, and Windows Explorer in dark mode, and Notepad++ in dark mode, and Omron Sysmac Studio in dark mode, and Autocad Electrical in dark mode, and Alibre CAD at the default (light gray) theme, and they look great. I'm in a nice, bright office, with (4) daylight 4' T8 LED bulbs directly overhead, and a whiteboard as the backdrop to my monitors, so it's not like I'm a recluse in a dark cave. The monitor brightness is not wrong.
At least, it's not wrong until I win-right or alt-tab over an Excel document or an old version of Studio 5000, where the color profile is stuck at black text on a white background. Then I'm instantly blinded. I can't set half the monitor (just the part over the Excel spreadsheet) to the right contrast and brightness to make Excel acceptable, because then I can't see better-designed apps.
And don't get me started on opening up a movie or game after work's done. "Set your brightness so the logo is barely visible." Yeah, no. "Game of Thrones is a cinematic show and therefore you have to watch it like you’re at a cinema: in a darkened room." Wagner and Snyder are watching their productions on studio-grade OLEDs. I won't put a show on the integrated screen of my old Thinkpad or Precision laptops, I know those displays are trash (and they're small, I only put stuff that's easy to see on them), but no brightness setting on my relatively nice IPS LCDs can comfortably handle the diversity of content they're used to display.
[1] https://webaim.org/resources/contrastchecker/?fcolor=828282&...
[2] https://webaim.org/resources/contrastchecker/?fcolor=999999&...
>Gee, this stark white brightness is hurting my eyes, maybe I should turn down the brightness on my display...
>Nah, I'll just demand every single company completely overhaul the CSS and contrast of everything while begrudgingly suffering the eye-burning whiteness of companies that haven't yet overhauled their CSS
Like wtf?
Instead, it varies wildly, often for good reasons... and then switching windows exposes you to extreme shifts. E.g. switch between photograph editing and a giant white text document, nothing's gonna save you then - stuff that looks correct and good for photography is absurd when most of your screen is the same as the sun.
Calibration is one thing, perceived brightness of the whole screen with specific content is another. And it's heavily influenced by how many nits are available, particularly since calibration will often try to use as much of that range as possible.
Taking it to the DPI example, having things built at a standardised DPI isn't about making everything appear the same physical size it's about making everything tuned against a consistent physical size for the exact same reason, default is always intended and your global adjustments are always consistently resulting in the source material being larger than intended or smaller than intended instead of "well, depends how uncalibrated the source was if it's still smaller or larger than intended".
You seem to be assuming the commenter you replied to didn't know that. As I understood it, all they were saying is that advice about calibration is useless for people who don't do photo editing, but whose problem is exactly that different windows have such wildly varying brightness that switching from one to another often makes everything look either pitch dark or third-degree-interrogation light in your eyes.
Which category of people do you think there are more of? My bet is on the latter. They need... Well, if you don't want to call it "another kind of calibration", you're free to come up with another term.
I like being able to see my phone in sunlight nowadays, but there have definitely been some tradeoffs.
No. You just use them in the dark.
To play PS5 I bought a monitor instead of a TV, because the place where I had to install the screen in the rented apartment is tiny, and tiny TVs are just crap with tons of input lag. So I got a gaming LG monitor.
Many PS5 games, specially those with HDR support, offer help in adjusting the brightness, often in the form of showing a very dark and a very bright image side by side, and telling you to adjust your settings until both are visible.
I found out that no matter what I do, this never happens. In the end the best setting is when NEITHER are visible. If the dark image is visible, the screen is so bright it feels like staring into a flashlight. If the bright image is visible, the screen is so dark that I can't see the contents of the screen with my curtains open or the lights turned on. I can't wrap my head around how someone can make a screen be so crap.
You, however, should stay in the dark.
I'm not the OP, but yes, going outside sometimes also hurts my eyes, depending on how bad the sun is.
Display manufacturers should really not just look at the maximum brightness but also the minimum.
Anyway, I prefer the ever so slightly beige Interface of Windows 2000. Same contrast and GUI esthetics, but less drab grey.
Yep. Without darkmode, my screens light up my neighbors fence like those Appalachian backyard streetlights.
I seem to recall that something like QtCurve offered buttons to do that within the scrollbar.
If only everyone did that, many time wasted in scrolling would be saved and "go to the top" buttons in websites wouldn't exist
We've hit peak usability about twenty years ago, in the Windows 2000 era. The screenshot in the article is actually from about that era, it's one of the early 10.x (10.3 I believe) OS X releases.
System 7 or 8, methinks. Clean, cool and collected.
Contrast is a factor yes, but the other thing that's happened with the flat UI epidemic is banishment of mid grays and light grays in favor of stark white and off-whites, making "light mode" much more bright looking than it had been previously. It's no wonder people were clamoring for dark mode after blinding flat UI had taken over.
That aside, high dpi displays are still a rare sight on desktops, there’s not many of them and the aspect ratios and ancillary features are extremely limited.
No, they aren't. ALL displays these days are high-dpi, when you compare to the 640x480 and 800x600 screens that were normal in the late 1990s. But the window managers back then were FAR better (in functionality and appearance) than what most of us use today.
Yeah they are.
> ALL displays these days are high-dpi, when you compare to the 640x480 and 800x600 screens that were normal in the late 1990s.
Leaving side your wilful misunderstanding of fairly standard concepts, no they are not: the monitors you are talking about were generally tiny, and the minor increase in median pixel density was largely counteracted by the blocky precision of LCD pixels.
For example, Macintosh was 72 ppi for a long time ( it is 109 ppi now).
My first LCD screen was 15“. And that was for a desktop, not a laptop. 17“ or 19“ were for rich guys or graphics designers ;)
Personally, I think it's just that monochrome icons are fashionable. I can't imagine that the GIMP developers for example chose to make GIMP's icons monochrome because that works better on e-ink screens.
For text and graphics, you'd generally want to use a higher-quality, lower-refresh-rate mode. Which is to say that there's quite a bit of established UI/UX knowledge that wants a refresh. I've distilled a set of basic principles: persistence is free, pixels are cheap, paints are slow, colour is (mostly) nonexistent, and the more ambient light the better. Paginated-navigation (whole screen changes in one go), line-art, and dithered or halftoned images work relatively well, raster images not quite so much, though can be acceptable.
<https://diaspora.glasswings.com/posts/638a8d10e041013afba844...>
For a demonstration of a wide range of displays (the best ones are featured last) as of 2021, see: <https://yewtu.be/watch?v=KdrMjnYAap4>
... I'm having difficulty finding e-ink / electronic paper market research, though one hit suggests an 8.5% CAGR: <https://dataintelo.com/report/global-e-ink-sales-market/>.
Using HN as a rough proxy, I see fairly substantial growth. Note that HN submissions overall have been fairly constant since 2012, per dang.
"e-ink"
2007: 1
2008: 7
2009: 14
2010: 18
2011: 24
2012: 28
2013: 24
2014: 24
2015: 16
2016: 25
2017: 22
2018: 39
2019: 35
2020: 60
2021: 88
2022: 84
"Electronic Paper" has minimal hits, though by years above: 0, 0, 1, 0, 1, 2, 1, 0, 1, 6, 1, 1, 0, 0, 8, 1."Digital paper" has an even smaller smattering of hits.
... though Apple has had monochrome devices (the original Mac, the handheld Newton) ...
... and often makes preparations years on advance for long-term strategic moves.
I'm putting very low emphasis on that last, as e-ink really doesn't seem to fit particularly well with the Apple ethos, except, perhaps, for watches.
But if Apple were planning, or even contemplating, an e-ink device, ordering a flat white UI/UX might be precisely the first step in getting there.
Many of these issues already exist, e.g., for documents which are likely to be printed on monochrome devices. Colour is useful where available, but it is not universally available.
(And that's before addressing issues such as colourblindness or other disability / accessibility considerations.)
My original comment was not at all specific to Apple (you'd introduced them to the discussion), other vendors, or any specific OS or application. Simply that monochrome and e-ink are increasingly concerns.
But since you raised the topic of Apple, and since, contrary to your initial statement that, broadly speaking, monochrome was "a display technology they never used", I'm both correcting the record, and noting that should there be a monochrome or e-ink prospect on Apple's roadmap, and further noting that Apple rather famously does not announce such roadmaps in advance, that flat/white would in fact fit with e-ink remarkably well.
What that has to say about whether or not Apple is contemplating any such move I am, of course, entirely ignorant.
Any explanation of the anti color trend must explain Apple's participation. Especially because Microsoft and GNOME appeared to imitate Apple.
I did not say monochrome was a display technology Apple never used. You named e ink. And monochrome is not a display technology.
Other trends included more transparency in content areas, links almost unidentifiable without color, and other reliance on small shade differences. And Apple made all app icons the same shape. All worse for e ink.
OK, that does it. You're a Hong Kong viking, not a Seattle baker.
No, light grey -- or some other light pastel colour -- and white.
Especially with this new "don't theme my app" movement. It's really unfortunate. The issues with CSS stylesheets in GTK should be solved with replacing CSS with a better way to describe styles, not with just throwing it all away and not letting the user set their own themes.
The developers basically say "fuck you" if your use case does not perfectly align with their "vision".
What I hate is installing a program that was designed for a KDE distro and because you run gnome all the icons are the same color as the background and alignments on things are whack.
Package it all up in a flatpak so it looks and works exactly the same on all distros. One complete and verified experience.
The user should be in control of his computer. That includes the programs on it. Locking it down so you can have "verified authentic design" is just straight-up user-hostile.
The programs can still be open source so you can recompile with whatever look you want, but they should bundle a working experiance by default.
But linux users seem more obsessed with curating custom themes over having things actually work.
Linux userspace is buggy, and I think this very-minimalistic approach sort of grown out from frustration about that. And they may be right, maintainers really don’t have the resources to do much better, especially when most frameworks they depend on has their own share of fatal, almost impossible to fix bugs.
The first type of CSS can be written succinctly, but the second cannot.
I suspect even their attitude towards theming done by end-users is more akin to ‘well sure, if you insist, you have the full source code, I can’t stop you, but you’re on your own’ than considering it a fully supported configuration.
There can also be legitimate reasons not to support it. On the top of my head, for example, the default theme being the most tested, etc., etc. In a perfect world, they'd all be tested and well integrated, but there's limited man power going around, and the world isn't perfect.
Though I otherwise agree.
Maybe distros are not doing a good job of this, but that is one thing they have the power to do. QT, GTK2, SDL, wxwidgets, and more toolkits I can't even think of should all fit together on my desktop and look the same. xfce, gnome, and kde all have some nice apps, they should mix and match. This is a HARD problem, but that isn't an excuse to not face it.
I would reject a distro that did this (unless I could disable it). But users should be able to make everything look the way that works the best for them.
We could shift cultural expectations so that distro maintainers become the first tier of support for all app issues in their distro, and escalate issues to app developers if and only if they've confirmed that the issue is distro-agnostic. That would be sustainable for app developers but could be a heavy burden for small distro teams.
> This is a HARD problem, but that isn't an excuse to not face it.
Agreed, I just don't think it's the responsibility of app developers to solve.
The concept of "white point" is often spoken of in terms of color, but brightness very much does matter too. It is painful for there to be something (especially something large) brighter than "white".
**
That said, we should have automatic dark mode based in inverting HSL's "lightness" (this can trivially be done directly in RGB, just check the min and max color channel of the pixel, then adjust all channels to flip them), rather than requiring ad-hoc color schemes all over the place.
CRT monitors had easy dials to quickly adjust brightness and contrast. You almost did it automatically without thinking when you had developed the motor memory. Nowadays monitor controls are often fiddly and awkward. But I still use them to adjust brightness to the environment.
Non-exhaustive list:
Linux: https://github.com/ddccontrol/ddccontrol || https://github.com/rockowitz/ddcutil
Works on both Windows and Mac
Twinkle Tray is an alternative: https://github.com/xanderfrangos/twinkle-tray
(Of course, that was a lot of money when we were both young...)
Up. Down. I'm really not sure....
When I was 20, the idea that my eyesight might have become meaningfully worse over time never really occurred to me. Fascinating.
In the physical world that'd be issues like bright points like car headlamps or street lights having a large corona/starburst, or if you're looking at a bright object against a dark background such as reading a book where it's lit in a darker room the 'bloom' will obscure what's behind it. On a screen with much brightness I'll get similar effects if there's contrast. I've been window shopping for a HDR display for a while now and wondering how much benefit I'd get out of it seeing as the main selling points are the brightness/contrast, especially when you're getting into the various forms of local dimming to present the media at its best.
For me, with (mostly-corrected) astigmatism and some (uncorrectable) higher-order aberration, dark on light is the only thing I can read fluently. The worst case is ‘black holes’ on a light page, as are fashionable for illustrating command line examples (and f—ing github's CI log view), especially combined with Las Vegas syntax colouring of varying brightness.
Earlier we had ICCCM (inter client communication convention manual). Now we have freedesktop.org.
Have you tried dark mode in Windows 11? It turns the entire window bar black, if multiple window bars happen to overlap it is impossible to tell them apart visually. On top of that in some programs it also turns the close/min/max window buttons completely black unless hovered by the cursor!
Microsoft should fire everyone at the company who ever made a UX design decision - except for the people who made the Windows Phone 8 UI, their only consistent and intuitive UI in the last 15 years.
The other criticisms are valid though, the last good Explorer UI was Windows 7.
I don't know what you mean about turning the window bar black. Did you set the theme to "high contrast"? I've used dark mode on windows since it became an OS feature and never had that problem.
Microsoft's UX has been poor since Win8, but not for graphical reasons. 10 and 11 look great out of the box - far better than any other OS I've seen, although tbf I haven't done much distro-hopping.
The first thin I do on MacOS is turn on the scroll bars. Yes, MacOS Has them set as "Only Show When Scrolling" by default, which is probably the most ridiculous setting.
Not having them take up screen real estate and working with most people's usage styles while being configurable for others is the right decision. The problem is systems and applications that don't let you configure them.
People talk about accessibility and their preferences like they are absolute truths— it's a lot more complex. Not having scroll bars sucks for people that never got comfortable with other scrolling input methods and people who use sight interfaces, for example. They couldn't possibly be less relevant to people who use screen readers, and as an input method rather than an Univision visual indicator, only slightly more relevant to people on phones and tablets. Phone and tablet usage has outpaced regular computer usage for quite some time, and that informs users interaction style. Adding visible UI elements adds cognitive load, and for people who never worked with scroll bars out of necessity, they're just another bulky animated distraction on the screen. Most younger users would probably think them about as useful as an always-visible on-screen keyboard.
I guarantee you— the designers at Apple who chose to hide those scroll bars probably thought more about scrolling more than every one of these commenters combined, and that was before they did formal usability studies.
Spot the indication that not all settings sections are shown in this screenshot, in all display settings and lighting conditions that your device might be used in.
* Were they ever there? I can't believe this dialog background - https://arstechnica.com/gadgets/2001/10/macosx-10-1/4/ - was the "winner" in any usability study. This was removed in 2003-11 with the release of 10.3.
b) Problems with specific dialog boxes or dynamically created features is evidence of problems with those dialog boxes or dynamically created features. As someone who's worked both as a developer and a designer, often the engineers win.
c) Assuming that these topics are simple enough for off-the-cuff reckonin' to validate or invalidate them are exactly why the engineers shouldn't win when it comes to interface decisions.
Of course I learned long ago and so I'm willing to accept that what was best practices back then might be wrong given new research that I'm not aware of. However this seems unlikely.
Or I go to the store and I buy heroin. I’m a heroin user and I use the heroin.
These UIs we speak of, are they hammers, or are they heroin?
Because I’m currently looking at a high contrast screen using a mixture of Unix tools created from the late 60s to yesterday.
I’m looking at an Excel spreadsheet made by a team of lawyers that is in a UI. The lawyers themselves highlighted and handled the contrast of the document. Beyond the table itself, Excel’s menu bar is easy to read for the basic operating needs of a spreadsheet. I mean come on, the pivot table UI is clearly masterful. (If Excel was a native plaintext tabular format and you could pipe stdin/out to the GUI app? Gimme!)
However, a lot of software is basically useless these days. It’s not designed from the beginning to be productive in any shape or form.
Some stoned dance by a junkie under a highway overpass is definitely some kind of expressive art form. How much more productive is the expressive art forms promoted by TikTok, Twitter or Twitch?
There’s clearly a scale at play. I’m as big fan of Twitch as much as I’m a big fan of the Buffalo Bills. I’ve always appreciated the sociological aspects of sports. To add some context to my definition of productivity, I would say that group sporting events are overall productive from a sociological perspective, be it IPL cricket or Fortnite tournaments.
TikTok is clearly and quite obviously towards the junkie dance scale of things.
From an experiential position there was not much of a difference between my observations of a woman filming herself doing a weird little dance on the sidewalk while completely oblivious to the rest of the world and the junky on the next block doing a weird little dance on the sidewalk while completely oblivious to the rest of the world. This basic object-level assessment of the actions that we and others experience with our physical bodies is core to the very notion of “meaning”. The “meaning” is just the stoned dance.
I know of no junkies famous for only being junkies but there are definitely TikTokers famous for only being TikTokers so don’t confuse this for some strict equivalence.
I’m just trying to establish a kind of framework for discussing the relationship between productive UI and productive software tools.
A hammer is useful for doing stuff, which modern UIs increasingly aren't. So it seems they aren't hammers.
From what I've seen from colleagues in the consumer space they've predominantly switched to A/B testing and statistical clickstream/log analyses, though large companies sometimes still do run lab studies for important decisions and to rationalize the giant one-way mirror they installed.
B) if you're doing dev work, you're probably not entirely cognizant of how different your software selection and usage patterns are than most people's, even for non-dev things.
C) there's a whole lot of interfaces out there and the great ones work so naturally and intuitively that you don't even notice them. Those are the ones for which many assume the design decisions were so obvious that they didn't even need designers. That's so so not true.Look at the most popular user-facing software: web browsers are all obsessed with usability (mozilla actually does some of the best open usability research out there.) Instagram, Tik Tok, Facebook, Twitter, et al... Incredibly clear and usable for their target market. Can't get much higher contrast than you do in email applications and other communication apps. There are tools to guage if your text color/background color/ and text size make for readable text according to the WCAG and I have never had a job, either as a designer or as a developer, where AA compliance wasn't a minimum for all functional elements. Most common user-facing interfaces that regularly use light or white text on colored backgrounds, like the iMessage interface or signal, benefit from OS-level accessibility enhancements like increased text size, which are very commonly used among the people who need them. My non-tech-savvy elderly relatives all knew about them through the setup process on their devices when they first bought them, and never looked back. Looking through every communication or other popular user-facing software package on my Galaxy U22 using a default theme shows nothing even remotely low-contrast.
This blind appeal to authority shouldn't convince anyone.
You haven't actually made an argument worth arguing about. It's devoid of value and it's not a productive addition to the conversation.
And don't bother wasting any more of my time. I don't care. You clearly have nothing to say.
"Informs"?!? Deforms!
WTF does phone usage have to do with sabotaging the UI on a computer???
This does not excuse making terrible user experiences elsewhere.
I have used MacOS every day for 10 years and i've never, except in exceptional circumstances, used the scrollbar to scroll. I don't see anybody in my circle using it. They all have the "Only Show When Scrolling" setting on.
I don't think this is ridiculous and I would enable the setting if turned off by default.
I also spend 99% percent of my time in full-screen mode in safari, vscode or terminal. So the top bar is also hidden by default. I think this is much more focused.
It is a choice, you can turn it on or off.
People with cataracts may benefit from dark mode. People with glaucoma or higher order aberrations (e.g. me) may benefit from light mode. Web sites should use `prefers-color-scheme`; native GUI programs should use the native equivalents (or default colours); command-line programs should not assume a particular background.
It used to be easy to adjust contrast and brightness on a display, volume on an amplifiee, an analog TV, a termostat, a car radio, etc.
I realize that we are not really on course (yet?) for reintroducing a lot of analog controls, but in the end, our world is analog. Input is analog via speech, muscle motion, etc. Output is analog, via light and other vibrations that reach our senses. Why isn't control more analog? It's probably a cost thing.
I would totally buy a display or a laptop with analog controls. I don't even care if the turn dial actually has 16M steps, so long as the response is pretty much immediate and feels like a real potentiometer. It should feel like direct manipulation and like you're in control, instead of these digital roundabout abominations.
As to the subject, I imagine having some knobs that I can adjust under different circumstances to quickly vary intensity or cycle through alternatives in order to make things more readable or audible.
90% Of what we do is in the browser today. Browsers could have an "accessibility" API such that turn knobs (bluetooth? whatever) could be used for control. Like scroll wheels but on steroids?
Dish forced a new remote on us last time a device broke and they replaced it. It has far fewer buttons. I’m sure it helps getting familiar with it on a super basic level. But the old one wasn’t that complicated anyhow.
But here’s the kicker: there’s no fast forward or rewind buttons. There no stop button. No record button. All of these (and more) have been turned into menu items and/or secret chords on the remote.
Oh. And it has a mic on it too. Hard pass.
Tv remote is just the easy example. I see it all over the place. Sleek no longer is pretty to my eyes. If I see something that I have to interact with these days and it looks sleek, I see frustration.
It's really a shame how user-hostile design can be.
I remember when Front Row for the Mac was announced. I loved Front Row (although the supported content was far too limited).
But despite Fromt Row’s limited functionality and simplistic interface, the Apple Remote still didn’t feel adequate.
It's like a 747 cockpit.
That’s another thing I like about the analog world.
Multifunction buttons… that never existed in the analog world? Or is that what is called “mode”? Send vs receive etc. Does anyone have a concrete example?
I’m not a remote control designer but I would think it would be fun to give it a try! Maybe I will :)
I like it.
Particularly if one thing affects another in a ripple-effect or chain reaction. It is great to be able to adjust at least two values at once. Keeps you from going back-and-forth adjusting in ever smaller increments to get to the settings you want.
generally most want to have a knob they can adjust and not worry about the underlying value. It's in line with the philosophy of tweaking settings and not using your eyes to judge if its in the right position.
I want actual physical knobs.not sure what that would be called. Potentiometers?
There are of course things where more specialized inputs are required, but for the rest, touchscreens are here to stay*
* One improvement I would like to see it about their surface — we can no longer blind type on phones, because we can’t feel the borders of the buttons - but I think we have the tech to dynamically make the screen’s surface rougher/smoother. Another idea is to bring back 3D touch (and potentially improve on that - maybe it could even take some 3D vector as input?)
That looks familiar somehow... How many leaves should I pay you for this insight?
I’ve seen this trend going on for over a decade now, like a slow parabolic arc. Somehow the aim of developers and designers turned around 180 degrees and became less and less about pleasing the users and more and more about impressing other people in your field. (Both programming and design.)
These scrollbars are absolutely pathetic, with no room for customisation. (good luck theming a locked-down application) It's blatant how UI designers don't give a damn about the users' needs, not even in FOSSland. I am not entirely sure why this is the case but it's a sad regression from the days when we had good-looking, functional, accessible and snappy software. Not locked-down, unthemable electron bullshit.
Also, we wouldn't need "dark mode" or the such if the UIs had any contrast and were legible.