GitHub-Dark VS Less

personally, I use dark reader for most websites. if it breaks (or doesn't look good on) a website that I use very frequently, I make my own stylesheet for the website. which is very time-consuming so it's not like I can do that willy-nilly. in some cases I can find an existing stylesheet that's better than dark reader. like for github I use github dark, which requires stylus. and if it's a website I don't use that frequently and darkreader makes it unusable, I just leave darkreader off. just suck it up and use the website in "light mode" for as little time as possible.

It doesn't have to be automated. You can use user style extensions to inject css made for the website. Like this https://github.com/StylishThemes/GitHub-Dark performance is pretty much identical to native and I still use it because the theme is better than the default dark theme.

StylishThemes/GitHub-Dark - :octocat: Dark GitHub style

Github theme: Github Dark

mrkrupski/LESS-Dynamic-Stylesheet - A set of useful mixins for LESS, the CSS pre-processor: http://lesscss.org

Now that we have addressed our scripts, we can focus on our styles. In this setup, we will look at the CSS preprocessor Less which lets us write CSS simpler, use variables and mixins. We can add it to the project with the following command: