Paru is a yay alternative. You can use either one. Just pointing this out since yay is mentioned in a lot of the other comments. I am not saying not to use paru. I am just pointing out that it is not something different. You can use paru instead of hay in any of the other comments in this thread. Or use yay instead of paru in this one.

You are better off using -Ss with yay than pacman. If you use pacman, it only searches the Arch repos. If you use yay, it also searches the AUR.

The only thing I have ever installed using Flatpak on Arch is pgAdmin. Inkscape from the repos works fine for me.

If you go the EOS route, yay is already installed.

With my IISP, the base package comes with 4 TB of bandwidth and I pay and extra $20 a month for “unlimited”.

I am not sure of “unlimited” has a limit. It may. It is not in the small print though. I may just be rate limited ( 3 Gpbs ).

I think anywhere outside the US or Australia will do.

I have 3 Gbps home Internet ( up and down ). I get over 300 Megabytes per second.

Can they not torrent a bunch of that bandwidth?

We have this guy saying we cannot build all the Alpine packages once to share with all Alpine users. Unsustainable!

On the other hand, we have the Gentoo crowd advocating for rebuilding everything from source for every single machine.

In the middle, we have CachyOS building the same x86-64 packages multiple times for machines with tiny differences in the CPU flags they support.

The problem is distribution more than building anyway I would think. You could probably create enough infrastructure to support building Alpine for everybody on the free tier of Oracle Cloud. But you are not going to have enough bandwidth for everybody to download it from there.

But Flatpak does not solve the bandwidth problem any better (it just moves the problem to somebody else).

Then again, there are probably more Apline bits being downloaded from Docker Hub than anywhere else.

Even though I was joking above, I kind of mean it. The article says they have two CI/CD “servers” and one dev box. This is 2025. Those can all be containers or virtual machines. I am not even joking that the free tier of Oracle Cloud ( or wherever ) would do it. To quote the web, “you can run a 4-core, 24GB machine with a 200GB disk 24/7 and it should not cost you anything. Or you can split those limits into 2 or 4 machines if you want.”

For distribution, why not Torrent? Look for somebody to provide “high-performance” servers for downloads I guess but, in the meantime, you really do not need any infrastructure these days just to distribute things like ISO images to people.

/s This was a Snap trap and you walked right into it!! You are right, Flatpaks are great bit you cannot use them for everything. We all need to switch to Snaps so we can build our base packages in them!

Not sure how much negotiating we have done. Nothing was committed to Trump that was not already in progress other than the “Fentanyl Cxar” ( whatever that means ). Probably it means giving that dumb American title to somebody already in charge of the border.

Trump got played.

The responsibility lies with Canadians now to wean ourselves off American products until a friendlier administration gets into office.

I use Arch and Debian. More issues on Debian for sure. Both have way fewer problems than Ubuntu. The myths around this really bug me.

Wayland runs great on the four 10+ year old machines that I have tried it on. Oldest is 2009.

A lot of the non-GNOME GTK desktops have elected to stick with GTK3. They even maintain a suite of applications (Xapps) that many of them share.

GTK 4 and higher are increasingly GNOME only (not that you cannot run them elsewhere—they just won’t fit in).

Arcan is a cool idea but you mostly hear about it from people complaining that Wayland is not ready. Of course, Wayland is already used by more than half of Linux users and Arcan does not really exist yet.

By the time GTK5 appears, a vanishingly small percentage of Linux users will need X11.

I run Wayland on 2009 hardware now.

As toolkits abandon X11, it is going to pressure other operating systems to move to Wayland as well.

FreeBSD is already moving. Even Haiku has Wayland support. So we are talking about the smaller BSDs and the Solaris derivatives. Or ancient operating systems on original hardware I guess. In which case, they can run the older apps which is likely all they can run anyway.

Worst, worst case, you can run Wayland on x11. If there is something you absolutely need, I guess you can run Wayland apps on x11 that way.

How so?

32 bit pointers take up half as much RAM as 64 bit pointers. A complicated application like a web browser consumes much more memory as a 64 bit app than it does as a 32 bit app. That is true of most programs but you are really going to notice it in both desktop environment and your web browser.

You would be amazed how much 32 bit helps. If you do not open too many tabs, the web should be fine. Video no problem ( at reasonable resolutions).

Q4OS with Trinity is a great pick for this user. Alpine is great but MUSL may cause problems. And I say this as a MUSL use (Chimera Linux). You are not going to find 32 but Flatpaks and Distrobox may be too complicated. So, I would stay away from MUSL based distros with 32 bit Linux on a 2 GB system.

MX and Antix are also Debian based and have 32 bit versions.