savedbythezsh

Lol chill, I use Firefox. I can still call out good things in other browsers even if I don't like the browser as a whole for other reasons. None of what I said there was in support of chromium.

Brave can make micro payments to content creators based on the number of views to the site, directly supporting content creators without ads or the need to join the patreon for each creator. It's a fully optional system, off by default but prompted upon opening the browser for the first time. It's a cool idea but they kind of spoiled it by making it be a crypto wallet with ads to earn the crypto.

Also, Brave doesn't have a subscription...?

Honestly, despite the crypto, good on Brave browser for trying to subvert the advertising model by providing an actual monetization alternative

Have you used fish? The built-in fuzzy matching works pretty well for me. Wondering if there's any reason to add atuin in. Sync seems like a negative to me more than a positive.

This is a fantastic write-up, thanks for sharing!

I use Jenkins for work, unfortunately, so I have plenty of experience

FYI, Jenkins has an endpoint to validate the pipeline without running it, and there's a VSCode extension to do this without leaving the editor: https://www.jenkins.io/blog/2018/11/07/Validate-Jenkinsfile/

FYI you can (sorta) redirect searches from the start menu: https://www.windowscentral.com/how-let-google-handle-cortana-web-search-results-windows-10

Mine all go to DDG in FF

The WinAmp maybe sorta open-sourcing is interesting. I've never used it (aside from downloading it to get MilkDrop working in Foobar2000).

I feel the same way. Designing good, opinionated APIs is HARD, but it also provides the best experience for both the author and the consumer.

• Prettier is the undisputed king of JS formatters because it has no options by design. You set and forget.
• One of the reasons iOS is so successful is because they lock down their APIs and put strict standards on apps, making it hard to write something that doesn't at least look good and slot into the OS well.

Among other examples.

In a world where your IDE and maybe also compiler should warn you about using unicode literals in source code, that's not much of a concern.

VSCode (and I'm sure other modern IDEs, but haven't tested) will call out if you're using a Unicode char that could be confused with a source code symbol (e.g. i and ℹ️, which renders in some fonts as a styled lowercase i without color). I'm sure it does the same on the long equals sign.

Any compiler will complain (usually these days with a decent error message) if someone somehow accidentally inserts an invalid Unicode character instead of typing ==.

These names are really fun! Good ones to add to my list...