The reasons we're seeing more of it are that developers are switching their bad hard-coded UIs to more flexible systems which allow it, and now that even MacOS/iOS supports it, there's an expectation for more and more apps to conform.
[1]: another valid case is apps with a strong emphasis on graphics: Photoshop, YouTube, Instagram, etc. A dark UI mitigates visual interference with the content.
Edit: but to be fair, I agree dark mode can be bad in some contexts like the examples you gave.
I very much prefer using light themes but I also record screencasts (400+ of them at this point).
Every time I run a poll asking folks if they prefer light or dark there's been a majority requesting dark mode in the recordings.
Personally I find the colorization of most dark themes having more contrast between the colors. A lot of light themes will make certain keywords dark colors which kind of looks the same on compressed video. I'm not sold on that being the reason most folks prefer dark themes, but I'm also not convinced light mode is better for video recorded content. I think with the right themes, maybe both are equal.
I've gone as far as writing a shell script to easily toggle dark and light mode for my terminal, tmux, Vim theme, FZF and other tools: https://nickjanetakis.com/blog/live-coding-a-shell-script-to...
All I end up doing is running `toggle-dark-mode` to seamlessly switch between the 2.
I know this because I have tried, with three different modern laptops (two MBPs and an XPS) which have the best brightness available for laptops. If I hit dark mode content, it just has to wait until I'm indoors. But usually I'm looking for something because I need it at that moment. If I can't view on potential illustrated video, I will try the next one I can view.
People taking the time to produce content often do care about attracting and keeping viewers/subscribers, and this is a case where an accessibility issue will reduce the number of viewers.
I highly appreciate the effort people put into sharing their knowledge, but I find it really disappointing when I can tell that their effort is wasted on some potential viewers. I may be weird (no, I am, but that's not necessarily a negative), but I know I'm not the only person with this opinion.
I have a $300 13" Chromebook with a 1080p IPS display and I spot check some of my videos on it. I'm able to read the text outside. Although I try to position myself to not directly have the sun glaring on the screen. That would be an issue to read anything, video or not.
I'm always for improving accessibility. If it's not too much trouble would you mind skimming one of my videos to see what it's like on your main device? Here's a video on creating a GPG key pair: https://www.youtube.com/watch?v=1vVIpIvboSg
Your video appears to be all in the terminal, and most text is white on dark background. Plus the font is bigger.
Contrast this (pun not intended) with an example of a colorful code video (not an ide, but representative of what you see in a lot coding videos https://youtu.be/zC7TcrRi46Q (not to pick on the producer of this video... just grabbed an example). This example is unreadable in bright ambient light, and there are many videos with about the same colors and fonts. These are the ones I'm talking about.
In the video you linked I see what you mean. I haven't tested it outside but just eyeballing some of the screenshots in the presentation the blue function names are likely impossible to read, the dark orange / red module names could be borderline too since it's kind of dark text on a dark background, and even the green atoms are a bit similar to the background in terms of darkness. I'm not sure what color theme that is but personally I wouldn't use it.
I try to stick with One and Gruvbox. Both have pretty decent contrast ratios for both light and dark variants. I have 1920x1080 screenshot side by side comparisons of both with dark vs light in my dotfiles at https://github.com/nickjj/dotfiles.
If it isn't, I usually just don't care or actually prefer white for some things like writing mails.
So I'm encouraging people to consider their audience. If there is no audience, then one has only oneself to consider :).
There are fundamental differences when designing for bright/day vs dim/night that benefits humans. In-car GPS was a specialised UI that paid attention to this earlier than our computers. The night UI maximised clarity in a low-light environment without being distracting. The day UI met the daylight with similar clarity. Never jarring.
Triggering a system-wide change across devices when the sun dips below the horizon is a nice start. The fact that it trickles even as far as webpage and VS Code theme is just awesome stuff.
Speaking to your detrimental cases, maybe the auto-change could be based on ambient light level rather than sunset time. It is certainly possible. Excluding the Nordics, the better solution is likely to move humans closer to natural light. Dim the room or build for natural light, rather than our screens able to be brighter to meet an artificial environment.
Both OLED and browsing in random low light environments often happen in the context of mobile devices. We do more and more on our phones. Because of that I wouldn’t treat OLED and low light as an edge case.
Kind of off topic, but I've always wondered why this is an issue. If I invert the colors, will those parts of the image suddenly compress just fine? Is it something to do with human perception of dark colors (like how many compression algorithms use more detail in various characteristics we're more sensitive to, such as brightness, as opposed to color)? That wouldn't make sense to me, as it seems to be a pretty obvious visual flaw.
I'm not sure, but I suspect that in general, dark mode syntax highlighted (highlit?) text is on average lower contrast than syntax highlighted light mode text. That could affect compression behaviors, perhaps.
Bold statement. I insist on dark mode everywhere and love it. Besides what compelling reason is there to give the user fewer UI knobs? We all have our own preferences.
And the points you mention are not a problem with dark mode but with low contrast. These can be fixed by increasing contrast.
What you're saying is akin to saying: "You like dark mode? Well you're wrong its bad for you." No thanks, not interested in your opinion.
If you are the only person viewing your screen, then by all means use whatever color scheme you like. I never said it was bad for you. I just illustrated when it is bad for some people.
Except in the cases of saving battery on OLED displays or viewing a screen in very low ambient light environments, dark mode is the wrong answer to a problem of an overbright display.
If content on a screen seems too bright, the solution is the turn down the display brightness. This is a choice you can make as your circumstance dictates. Dark mode is a nice option for a few cases, but it should not be forced upon anyone.
There are two cases where dark mode is a really bad thing:
1. You're presenting your content via a projector in a room full of people (and a room full of people will have some ambient light, because safety rules generally prohibit trapping a lot of people in pitch darkness). No matter how many lumens the projector can put out, they will not make your low contrast content as visible as light mode would have been. Most often, the ambient light of the room will completely wash out the low contrast projected image.
2. You're making a screen recording of your content to demo or educate others (Youtube, etc.). The low contrast, colorful text will not compress as accurately as light mode, so the resulting text will be blurrier than if it were in light mode. So it will be harder to read compared to light mode content. Plus, if your viewer happens to be in a bright room or outside, your content will be unreadable. You've just wasted your good effort by limiting your audience.
Edited typos :(