jerb

Look into the app Repainter. It isn’t free and needs root or Shizuku access but does the trick.

It’s honestly gotten to a point where I don’t even check ProtonDB anymore unless it’s a brand new game. Generally things just work.

Are we sure this isn’t just for clarity? “Language model” implies Bard and such already as they’re more formally called “large language models.” While I don’t like that they’re doing it, I think it’s very likely they’ve been publicly scraping information for quite some time (in fact, for an LLM like Bard, they pretty much have to!), and have just changed the wording to fully disambiguate between Google Translate and Bard.

I can agree with this, my Darter has horrendous battery life and had a ton of bugs that made the thing really annoying to use until a recent BIOS update. I can’t help but feel like I got burned.

Next laptop is a Framework for sure.

Isn’t Endless immutable?

You realize Opera is the exact same engine, right?

I think there’s still value in it from being a DE-agnostic GUI solution, for what it’s worth.

That’s because of a difference on protocol (iMessage vs SMS). This wouldn’t matter if they chose to support RCS which is effectively the Android iMessage equivalent and is an open standard (on paper, not necessarily in practice) but that will never happen.

It does take some adjusting- the pitfalls you’d encounter with Distrobox on Universal Blue are the same as Distrobox on any other distro, so first I’d say to try moving your workflow to Flatpak and Distrobox on your current system or a VM and see how it works out. Generally Flatpak is preferred to a rootless Distrobox which is preferred to a rootful one, but sometimes there’s not a Flatpak for something (especially command line tools) and you need access to hardware or system level stuff that only a rootful one can do properly.

Not particularly, the workflow on your Arch system will be the same as any other distro, that’s the nice thing about Distrobox.

I would highly recommend looking into the distrobox-assemble command, though: it lets you declaratively build distroboxes with the packages and config you need on them. I have a personal box which operates as my primary terminal that’s automatically destroyed and recreated on every boot. This way, the packages I always use in a terminal are available, and I can add something I need temporarily with no issue without worrying about forgetting about that package being there down the line and causing some weird update failure or general bloat.