> 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 wh

> 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.