I tried it a while back in Firefox and after a a few days I noticed memory usage in Firefox was going way up and whenever I opened dev tools everthing would slow down drastically. Removed the addon and everything went back to normal.

Anyone getting these types of issues still? I would love to start using it again.

Dark Reader is great if you do not care about performance.

Cool browser!

Really nice, thank you

Yes, essentially yes. UserScripts used by GreaseMonkey are JavaScript. UserStyles in Stylus work analogously for CSS.

Thanks Krasnol :)

This is an interesting issue. What color is your "topbar" configured to? You can check it under your profile settings: https://news.ycombinator.com/user?id=Krasnol. It could be that the topcolor that you've set is a dark color, and the CSS inversion makes it light, thus conflicting with the text color.

If this is still a problem, please do open an issue on the GitHub repository, I'll happily look into it :)

I, too, appreciate HN's reluctance to add new features, and have zealously followed the same approach in maintaining my own tiny corner of the web for two decades.

But dark mode offers such immense retinal relief that a few lines of CSS¹ does not seem too unreasonable, especially since it means not having to trust third party extensions to do the job (though Firefox supports site-specific CSS rules natively: https://superuser.com/a/319322/38084 ).

¹ I arrived at these few lines for my simple site:

  @media (prefers-color-scheme: dark) {
  body {background: #222b39;color: #e1dfdc}
  input,textarea {background: #333;color: #e1dfdc;border: 1px solid white}}

though HN likely requires a far more skillful and circumspect approach, e.g., https://news.ycombinator.com/item?id=23199649 .

It’s also one of the things I value highly.

The other is the better signal/noise ratio.

Does dark mode help those with visual disabilities?

I whole heartedly want dark mode HN but your comment seems insincere and hyperbolic.

I know "could be made in 5 mins" is an exaggeration, but there's a very real long-term cost to adding thematic options like dark mode that HN just might not want to take on.

Any time you split your UI (for example, light mode and dark mode), it effectively doubles/multiplies all future UI testing you do from then on out (testing all new views/features on both light and dark mode). It can also add additional strain on bug reports / support, since you no longer know what UI configuration a particular user might've been using when they complained about something.

Slightly less of an issue on a site like HN where the UI is somewhat simple and static and changes happen at alligator speed, but still a long-term commitment to make (as opposed to 5 min of dev time).

(In case it isn't obvious, I'm a little salty about how much time I still spend testing/fixing my own site changes in dark mode over a year after adding it.)