Nobara is just Fedora with a heavy layer of gaming-focused polish applied. In that regard it’s quite a bit more familiar than something like Arch, which makes a point of not holding anybody’s hand, and (just in terms of ease of use and overall userbase) feels a lot closer to what Gentoo was like back when I last was in this space.

I was heavily in the camp of Debian-based distros back in the day, but Debian proper has never been a great choice for desktop, and Ubuntu’s star is much faded of late, so I decided to give an RPM-based distro a chance before jumping way off into the deep end. I don’t have the time to fiddle that I used to, and (at least until yesterday’s hiccup) Nobara was much closer to “it just works” out of the box than anything like Arch would have been.

I’m an ex-sysadmin so I guess I get to be the middle head, but blundering my way through the current distro scene after not having touched a desktop Linux install in, oh… twenty years or so, I feel more like the right. I suppose on the one had I had the good sense not to jump right into Arch or Nix, but even more familiar territory like Nobara has its pitfalls. Just today I had to clean up a botched release upgrade because the primary maintainer had left conflicting packages in the repository for an extended period. Not laying blame per se, that’s what you get when you sign on to a one-man effort, but it was a real pain in the butt to diagnose and correct.

I’d been planning for a new HVAC system for a while when that video came out, and it gave me the idea to cross-check the thermostat data with the Manual J calc I’d already done. They were in general agreement, though the Manual J block load was more conservative than empirical data for a design day.

In your case, since you don’t have data from a healthy system on a representative heating design day, I’d suggest using a web tool like CoolCalc to simply calculate an approximate Manual J total heating and cooling load, and use that to guide your choices.

A little headroom ain’t bad, but it had three times the required heating capacity for my area’s “design day” low, which meant that for most of the winter it was kicking on for maybe 5-10 minutes per hour and then leaving massive cold spots in the house, because the thermostat was smack in the middle and all the walls were bleeding heat.

My new heat pump is just about 2x the design day heat requirement, but that also means it’s got capacity to handle extreme lows without resorting to resistance heat, and in any case it’s fully modulating so the house has stayed quite comfortable so far.

My old furnace was hilariously oversized for the house.

One of the nifty things about smart thermostats like Ecobees is that you can pull usage data from their web portal. I grabbed a CSV file covering a cold snap last year that reached a 100-year record low, and using Excel I summed up the total heat output while we were at that low.

The furnace was only running 50% of the time, even when it was with a couple degrees of as cold as it’s ever been where I live.

Needless to say, when I got a new system installed I made sure it was more properly sized, and given that I had a convenient empirical measurement of exactly how many btus I actually needed in the worst case as scenario, that was easily done.

Problem is that if you’re looking for FOSS software outside of the absolute most mainstream use cases, that type of software is the only available option. GIMP and Inkscape have been mentioned but throw FreeCAD into the ring as well. Shotcut and Kdenlive are passable, but don’t quite measure up to the commercial alternatives.

My particular hobby horse is CFD code. OpenFOAM is fantastic from a technical standpoint, but until recently, to actually use it you either had to buy a commercial front-end, or literally write C++ header files to set up your cases. There’s a heroic Korean developer who’s put together a basic but very functional front-end GUI in the last year to change that, but it only covers relatively straightforward cases at the moment.

My first attempt to switch to Linux for my primary desktop was in 2007, and ended when my attempt to run WoW via WINE mostly worked, but had a weird an completely unfixable audio delay.

Proton (and Valve’s efforts on SteamOS and the Steam Deck more generally) have been an absolute godsend for Linux as a usable daily-driver.