For those that don't know, on Settings > Appeaarance there is a setting for "Use a fixed-width (monospace) font when editing Markdown". It's already a good QoL improvements (and it should be the default, honestly).
At the beginning of Gitcasso, I took a little survey of GitLab, Reddit, ChatGPT, Claude, etc. to see how they were doing their textboxes. Of those I just listed, GitHub is the only one still using a plain textarea, all of the rest have a wysiwyg richtext gizmo (with GitLab and Reddit you can opt-in to markdown).
But by using the same variable-width font that the rendered comment uses, GitHub's default gives you more of a wysiwyg experience than a monospace font does. With syntax-highlighting it's an even more wysiwyg feel, but with absolutely none of the content ambiguity that richtext normally brings with it.
I came away really impressed with GitHub. For any given decision, it's hard to tell if the market victor won because of their good taste or if they won in spite of that particular decision and there was somewhere else where the good decisions were decisive. But as the GitHub issue/PR commenting system stands today, I have a hard time finding much to gripe with (except the missing syntax highlighting, of course).
At the time I created it, I worked on Windows more often and I had a lot of trouble trying to find a Make build that works fine on Windows. The ones available for Windows are usually incompatible with the GNU version. So cross-platform support is one advantage of alternative tools.
Other than that, Task has a lot of features, so some use cases are not covered by Make.
That said, I'm not a Make hater. If it works for you, that's absolutely fine. Many people has found value in Task, though.
Congratulations on you project, hope to have once a project as succesfull as yours.
I would like to clarify that I don't mean to bash Task, just tired of critiques saying that Make is bad because is old, and Just and Task are better only because they are new.
Passing parameters kinda sucks, someone else made a comparison in another thread about named parameters and how easy it is to pass and define them in Just. Love taskfile otherwise
Personally I disagree, I think `--` is very intuitive.
Maybe it isn't super common knowledge, but `--` is in line with the POSIX argument parsing convention[0] and is used by many (most?) GNU/BSD tools and many other tools such as `kubectl`. This StackOverflow thread[1] also has some information about it.
I use dark reader, but I just know one day I'll wake up to news that it had secretly been sold a month prior and had been doing all kinds of nefarious things. This is inherently a problem with browser extensions that both auto-update and basically require access to every website.
Good thing that more and more site and apps are supporting dark modes as time passes. Many supports automatic switching based on OS/browser setting as well, what is great.
I dream with the day where this extension won't be needed anymore. Hopefully HN itself will support it someday.
I have it setup to enable according to the system. Also, I use the whitelist mode, so I enable on specific websites instead of having it enabled for every one automatically.
for anyone trying this for a first time, after installing, click the icon, click more, and there are 4 ways to darkmode a site. filter, filter+, static, dynamic. youll find different ones work better for different sites. then go back to the filter tab and modify brightness and contrast. sometimes the filtermode that is not immediately the best looking "works" the best once fixing the contrast.
Darkreader seems to always induce a noticeable performance hit on each computer I've ran it on for some reason when I run it with the default settings. I may try your whitelist method instead and give it another chance...
