It makes snese they want to distance from the Minecraft name for that. Engendered annoying “but muh Minecraft” expectations, and there’s already the Mineclone2 aka Voxelibre “subgame” for grabbing that attention.

Oh no by all means do preach. I was just about doing the same about schroot. :p

And, like I said, it’s not that I don’t like it. It was just too much for the rather small usecase I had back at the time. I’m pretty sure if at some point I move to a distro less featured than Debian Sid I’m gonna have to pay more attention to Flatpak and Nix again.

I basically took the general idea from this Ubuntu doc and made som changes. After installing debootstrap, I followed these general steps:

• set up an user for Steam, with adduser steam.
• created a directory to host the “virtual machine” at /var/lib/chroot/steam64.
• used the page linked above to create a schroot profile directory with the chroot data I want.
• used the page linked above to create a schroot profile entry for the chroot, adding steam as one of its allowed users.
• set up an Ubuntu 18.04 schroot with the following command: debootstrap --variant=buildd bionic /var/lib/chroot/steam64 http://archive.ubuntu.com/ubuntu/
• on the host, allowed cross-“host” applications to lauch windows with xhost +local:.
• once completed, entered the schroot as root and added the needed i386 arch and packages for Steam and for bubblewrap / Chrome containerization.
• still in the schroot as root, installed enough packages for a basic graphical environment (basically: a text editor, xnest and xterm; between their dependencies, they’ll take care of most of everything).
• exited the schroot.
• entered the schroot as steam and fired up the Steam launcher manually.

It’s not perfect, there are a few issues (in particular with audio) but once I had the installed schroot ready, I never had to worry about its 32-bit packages ever again. And that was back in… like, 2019 or something. Six months ago I copied to old schroot to my new machine and resumed playing, with no more cost than having to set up the schroot packages and the steam user (with the same old UID) on the new machine.

Here’s a sample of the schroot profile file I’m using. The “steam64.local” is the profile directory, which is basically a copy of schroot/buildd (or of schroot/minbase) with some configurations in fstab and copyfiles to account for eg.: isolating /var/run and dbus, and giving the schroot access to the home directory for the steam user.

Tried Nix once, I liked it but overall found it too complicated to setup and manage for the [counts fingers] three programs I was using it for. Might be worth the while if I need a larger library of programs from Outside, but so far Debian and AppImages have not failed me.

Part of the problem is, sure, that installing an entire arch for a package touches up a lot of stuff… What I did was I set up a debootstrap schroot and added i386 arch to that so that neither they nor Steam touch my main system. Not only did I never have problems with Steam again, but I actually resumed pretty much from what I was when I got a new machine, simply by copying the schroot files over. Didn’t even have to install anything (but the schroot serve on my new system itself).

I think they mean the original.

And that’s why IMO the project should ensmallened. Instead of trying to catch up to everything bloatware internet and Google are doing, Neo Firefox / Neo Mozilla could instead focus on developing a subset that’s lean and safe to use (no JS, for example) or even promote and offer first-class support to alternative internets like Gemini (the actual one, not Google’s namesquat).

There are still versions of Opera with their own original engine going around.

Damn, Presto should return. That thing could load like 300 tabs in like 30, maybe 60 MB RAM tops.

C:

Problem → return Solution;

C++:

Problem →

const [auto]&& (Problem&& problem) noexcept(noexcept( Solution<Problem>{}(std::forward<Problem>(problem)) )) { return Solution<Problem>{}(std::forward<Problem>(problem)); } -> decltype( Solution<Problem>{}(std::forward<Problem>(problem)) )