For me, most dark mode styles are awful (jet black background bright white text). I'd rather have per website toggle so I can apply my own styling when the site's styles suck.
But you can have both? Automatically switching between light and dark mode based on system preferences is handled by CSS, which you can override with your own styling.
I have found it incredibly hard to override dark styling, at most you're modifying/merging styles. Dark reader extensions don't work well turning a dark site light, and I've had limited success injecting styles with tampermonkey/stylus. Of course it can be done, just override every style set by the site. But this involves setting a lot of styles and must be done case-by-case rather than using an auto styler. The only thing that works reliably in an automated way is starting with a light style and then modifying it to dark styling.
I also detest the conflation of OS dark preference, browser chrome theme preference, and website rendering preference. It should be obvious to anyone that these are three different concepts where people can have different preferences for each. The cargo-culting in silicon valley drives me nuts.
> But this involves setting a lot of styles and must be done case-by-case rather than using an auto styler.
If the website is using modern CSS then the colors would be set via CSS variables instead of being set inline in lots of places.
> I also detest the conflation of OS dark preference, browser chrome theme preference, and website rendering preference. It should be obvious to anyone that these are three different concepts where people can have different preferences for each.
Most people definitely prefer consistency so I don't think it is unreasonable to default to following the system preference.
I don't mind the default, but it's the lack of customization in most apps that is a severe oversight. I can't change my theme in the OS without it telling apps I want a dark theme (I don't). I can't change the theme in the browser with it telling every website I want a dark theme (I don't). There are no overrides to force the website rendering theme to be decoupled from the browser/OS theme. In everyone's mad dash to implement a dark theme, no one stopped to think for half a second. It's asinine.
The point of using a framework is to reduce mental load at expense of customizability. The moment you need to change something in the framework - this mental model falls apart.
Obvious solutions are to vendor your dependencies (compile the framework from owned source) or to drop to the lower level of abstraction.
LLMs should have no problem using browser/node APIs directly since they're very well used, well documented, and not changing as much as higher level software does.
Sure, but would that be one that contains services and apps ordinary people use everyday, or would they all have jumped ship like Netflix did? That version would still be an open web, just a very different one.
Why all software needs to constantly evolve and grow with features? This is how you end up with what Postman has become.
reply