If you’re not on it already, join the discord. Lots of helpers there. I recommend sticking with Bazzite and learning how to use it better. It has the tools you need to run anything you could run in any other distro. You just can’t always copy and paste commands from a Google search. But that’s where the discord can set you straight.

Bazzite > Bluefin > Aurora in usership from what I’ve seen. I started on Bazzite KDE but ended up staying with Aurora.

I can’t stand GNOME, but I understand that other people like it.

People who say Bazzite isn’t for tinkerers just misunderstand it. It’s extremely tinker friendly, just not in the ways people are used to.

I’d say it’s actually a lot more tinker friendly because it’s super easy to revert changes.

I chose the middle option for things I’m not hosting, but could see myself hosting in the future.

The worst part about quadlets, IMO, is that they don’t use the same key words as podman run does. So turning a working podman container into a quadlet can be challenging.

I’m in a similar boat. The difference for me is that I can definitely tell times where I’m faster. But there are still times where I fumble around. I know that eventually, I’ll be way faster using vim motions than I ever was without them.

When I first started actually trying to use it to do work, it felt pretty bad. But once I got over the hump it felt better.

I think I’m at the point where I’m at least as fast as I used to be, if not slightly faster.

Despite getting ragged on for it, I really enjoyed the game. It wasn’t spectacular, but I found it fun.

The ease of switching really just depends. Myself, I’ve had several stumbles switching, but I’m still so happy I did and I’m not going back. My wife on the other hand, has had no issues switching from her Chromebook, because she’s a super basic user who spends all her time in the browser.

Check out Tailscale. It uses Wireguard under the hood, but it’s magic.

containers should be immutable and not be able to write to their internal filesystem

This doesn’t jive with my understanding. Containers cannot write to the image. The image is immutable. However, a running container can write to its filesystem, but those changes are ephemeral, and will disappear if the container stops.

There’s a good deal of misinformation here. The main part being disk space. While it is true that flatpak apps will take up more space, it’s not nearly as bad as you think it is. There is a lot of really good optimization going on under the hood that you don’t see. Dependencies are de duplicated. I’m no expert on it, but I believe that dependencies also have delta changes from one version to the next.

Regarding apps not supporting building of the source, you should get over that or do the work of supporting it yourself. Open source is a hard, usually thankless job.

Depends on which stream you choose. Latest and stable-daily have it now. Stable will have it tomorrow.

Didn’t be so hard on yourself. You can also pester us about the status of Jira tickets.

So, slightly tangential, but I have a failed home automation project this past week.

I have been using an unofficial integration for my mini-splits for a few years. The guy who wrote it likes to disappear for 6 months at a time and it seems like it may be abandoned. It finally stopped working after a home assistant update.

I had bought some ESP based replacement dongles about a year ago and decided to finally use them. Well, not all of the features worked, so I set about writing my own firmware.

That ended up working even less well. I wasted a lot of time and effort trying to get my firmware to work before giving up and just moving to the fork of the original Home Assistant integration for the official dongles.

I hate being beholden to third party stuff like this because I have robust automation setup for my mini-splits and updates can completely break them and be a massive pain to fix.

I’m not sad I tried and failed so much as I’m just sad it didn’t work. I may try again sometime in the future.

Wait. You want anti-corpo social media, but not anti-corpo discourse??

I have no horse in this race and tend to believe the poster, but those comments have no context and make no sense to me.

That’s what Distrobox is for. It’s super useful.

Have you looked at any of the Universal Blue OSs based off of Silverblue? You can rebase to them extremely easily and try them out with no risk.

https://universal-blue.org/

All of Linux requires specialized knowledge. Immutable just takes different knowledge.

The real kicker with that is just that you can’t always just follow instructions you find online. Usually you can, as long as you’re doing them in a Distrobox, though.

I went with immutable as a newbie, and I think it’s great. It feels like getting in on the ground floor of the future.

One of the incredibly cool things about Bazzite (and all of the Silverblue based OSs) you can very easily rebased to another flavor. The only caveat is that apparently the Gnome flavors will cause issues with the KDE flavors or something. It’s a Gnome issue from my understanding.

Rebasing takes a few minutes and a reboot, and you can easily revert it.