GigglyBobble

Oh, come on, that's not gay! How would you fence with limb dicks?

Your quote is worthless, that summary doesn't give any reason what's problematic about the browser.

It's also unfortunate that the article's author chose to start with politics - I prefer technical reasons to stop using technical tools.

The crypto bullshit and injection of affiliate codes to URLs are indeed problematic. However, to me that just says to stay vigilant when using Brave but it's still not as bad as Chrome.

Personally I use Firefox anyway but unfortunately, webdevs get lazier every year and only test Chromium browsers and sometimes some stupid website doesn't work correctly on Firefox. If it's something like an airline checkout I need a fallback browser and today that's Brave.

I usually merge because I like to see commit history as it happened and because rebasing multiple commits with conflicts is more time-consuming than fixing it in one merge commit.

I do rebase smaller changes though to reduce merge commit clutter and like interactive rebase to clean up my local commit mess before pushing.

Merge commits suck.

My biggest issue with GitHub is that it always squashes and merges.

You are aware you're talking about two different pieces of software?

If your cherry-pick doesn't run into conflicts why would your merge? You don't need to merge to master until you're done but you should merge from master to your feature branch regularly to keep it updated.

The cringe term "code ninja" supports your theory.

Firefox is a weird buggy mess that constantly freezes.

This is definitely not normal, Firefox never freezes for me. May be worth checking that out, especially your extensions.