Studio monitors are excellent choices, but expensive. I've used genelecs for pretty much every audio workstation I've ever done, I'm a huge fan, but you're also talking $800 and up.
You can sometimes find a good deal on some used studio monitors, which to me is the way to go. A long ways back I decommissioned some genelecs for a studio (surprise surprise, the new studio had newer versions of the same model), and I've been using them since at home. Roughly 15 years now.
I wouldn't say they are wrong, I've got plenty of issues with Firefox that aren't in chromium-based browsers. Mostly with media playback, but on Android the toolbar hide on scroll is a mess, no matter what it just covers the page. Makes it really hard to use a menu or click a button depending on where it is. I also have some locally run services that throw js errors in FF but not in cromite, chromium, or chrome.
Doesn't mean I don't prefer FF because I acknowledge it has problems. I don't generally view videos in my browser anyway, and I disable the hide-on-scroll feature. And if I have a particularly problematic site (the js errors), I open cromite or whatever.
The bigger issue isn't people talking about bugs, but downplaying the role the foundation plays in supporting users. That, imo, is where a lot of misinformation and disinformation seems to live.
This is why Debian is my server of choice, and my work desktop of choice.
OP, There are some flavors of Debian out there that are more rapid release, like LMDE, Siduction, Sparky, even Kali (though I wouldn't recommend Kali as a primary desktop personally). Some based on Sid, some based on Testing.
Like anything else, it's good to know how to do it in many different ways, it may help you down the line.
In production in an oddball environment, I have a python script to ftp transfer to a black box with only ftp exposed as an option.
Another system rebuilds nightly only if code changes, publishing to a QC location. QC gives it a quick review (we are talking website here, QC is "text looks good and nothing looks weird"), clicks a button to approve, and it gets published the following night.
I've had hardware (again, black box system) where I was able to leverage git because it was the only command exposed. Aka, the command they forgot to lock down and are using to update their device. Their intent was to sneakernet a thumb drive over to it for updates, I believe in sneaker longevity and wanted to work around that.
So you should know how to navigate your way around in FTP, it's a good thing! But I'd also recommend learning about all the other ways as well, it can help in the future.
(This comment brought to you by "I now feel older for having written it", and "I swear I'm only in my fourties,")
Creating a bug report or feature request can be done without having to create an account, and the backend tools (including blocking instances) are being completed first.
It's not like it's forced either. You can just run it local and have no federation (once the feature is out of course, right now you wouldn't have it regardless).
For one thing, more FOSS focused. It's lighter/faster for me than a self hosted gitlab, there is nothing hidden behind a paywall, they are working on some nice activitypub integration, actions are really handy (yes it's a bit of yaml soup), codeberg is using and supporting it, a better focus on security and stability than gitea (where it forked from), the ux is clean, and that's about what I can think of off the top of my head.
Mythbusters streamlined is like that. A bit rough on some cuts imo, but overall just cuts the fluff.