3 ms·

I was just supplying one reason for changing it, other people may just prefer some particular site or application in light mode versus dark (and vice versa) ins

I was just supplying one reason for changing it, other people may just prefer some particular site or application in light mode versus dark (and vice versa) instead of managing multiple instances of the same thing like I am. Suppose you're editing documents and your word processor has dark mode, but you want it to always be in light mode. With the described control in the article you would have to change the behavior in the evening, specifically, to get it to stay in light mode permanently (or change your system settings to be opposite your normal settings, switch it to light, and then switch your system settings back). There is no way any one with any common sense can think that this two-choice option (one is magic, one does what you would expect; which is which depends on time of day for many users) is better than a three-choice option where each choice does exactly what you'd expect.

xp84 2mo ago
> Suppose you're editing [...] but you want it to always be in light mode. Your whole objection here hinges on you coming to that realization during the day when it's already in light mode by default. The 99.9% likelihood of "When does a user decide to go looking for the dark/light settings?" is "when the current color != the color desired. For your above scenario you'd go in there the first time you used your word processor at night. You'd flip it exactly once, and it would do what you described you want - stay light forever. Perhaps you're the kind of nerd like me who likes poking through and tweaking every available setting of an app proactively, just for fun... and I'd expect VS Code for instance, to be optimized for "us." But the vast majority of people would never go hunting for the setting to "make it always light" at the time when it's already light. The thesis here is that, for apps not designed for developers, it's probably more valuable to not have those who aren't nearly as expert have to wonder if they're picking the wrong choice by offering a third option.

xp84 2mo ago

> Suppose you're editing [...] but you want it to always be in light mode. Your whole objection here hinges on you coming to that realization during the day when it's already in light mode by default. The 99.9% likelihood of "When does a user decide to go looking for the dark/light settings?" is "when the current color != the color desired. For your above scenario you'd go in there the first time you used your word processor at night. You'd flip it exactly once, and it would do what you described you want - stay light forever. Perhaps you're the kind of nerd like me who likes poking through and tweaking every available setting of an app proactively, just for fun... and I'd expect VS Code for instance, to be optimized for "us." But the vast majority of people would never go hunting for the setting to "make it always light" at the time when it's already light. The thesis here is that, for apps not designed for developers, it's probably more valuable to not have those who aren't nearly as expert have to wonder if they're picking the wrong choice by offering a third option.