The AUR still has a lot of niche software that hasn’t been Flatpakked, but yeah. Flatpaks are way more convenient, especially for large software where AUR compilation can take a long time.
you probably only compile on one thread if you have a default /etc/makepkg.conf
though compiling a firefox browser on 12+ threads still takes several minutes up to half an hour
(try doing that with a chromium browser, thats hours rather than minutes)
Agreed. DaVinci Resolve Studio and Blackmagic hardware drivers are examples of that kind of niche software that I use on a regular basis. The only supported route for that stuff is RHEL/CentOS, and those don’t seem particularly well-suited to my main machine’s other purpose, which is games. If someone’s already done the legwork to solve the problem for Arch, and the build files check out, why reinvent the wheel?
Additionally, it’s the only distro I could get Resolve Studio working on with an AMD GPU consistently.
For the most part, though, the official repos and Flathub give me what I need.
Agreed. DaVinci Resolve Studio and Blackmagic hardware drivers are examples of that kind of niche software that I use on a regular basis. The only supported route for that stuff is RHEL/CentOS, and those don’t seem particularly well-suited to my main machine’s other purpose, which is games. If someone’s already done the legwork to solve the problem for Arch, and the build files check out, why reinvent the wheel?
Additionally, it’s the only distro I could get Resolve Studio working on with an AMD GPU consistently.
For the most part, though, the official repos and Flathub give me what I need.
The AUR still has a lot of niche software that hasn’t been Flatpakked, but yeah. Flatpaks are way more convenient, especially for large software where AUR compilation can take a long time.
The other day I died of old age compiling Librewolf from the AUR
What’s wrong with librewolf-bin? Would you choose the Flatpack or the bin from the AUR?
I ended up going with librewolf-bin. The flatpak version had some issues for me because my configs are a spaghetti nightmare
you probably only compile on one thread if you have a default /etc/makepkg.conf
though compiling a firefox browser on 12+ threads still takes several minutes up to half an hour
(try doing that with a chromium browser, thats hours rather than minutes)
Agreed. DaVinci Resolve Studio and Blackmagic hardware drivers are examples of that kind of niche software that I use on a regular basis. The only supported route for that stuff is RHEL/CentOS, and those don’t seem particularly well-suited to my main machine’s other purpose, which is games. If someone’s already done the legwork to solve the problem for Arch, and the build files check out, why reinvent the wheel?
Additionally, it’s the only distro I could get Resolve Studio working on with an AMD GPU consistently.
For the most part, though, the official repos and Flathub give me what I need.
Agreed. DaVinci Resolve Studio and Blackmagic hardware drivers are examples of that kind of niche software that I use on a regular basis. The only supported route for that stuff is RHEL/CentOS, and those don’t seem particularly well-suited to my main machine’s other purpose, which is games. If someone’s already done the legwork to solve the problem for Arch, and the build files check out, why reinvent the wheel?
Additionally, it’s the only distro I could get Resolve Studio working on with an AMD GPU consistently.
For the most part, though, the official repos and Flathub give me what I need.