I’ve been using Homebrew on Linux for several years and never had an issue. As others have said, it will not be able to provide GUI applications (in most cases) as on macOS, but it is a great way to get system and indie software alike
Thank you for your input, it’s heart-breaking to hear that it’s not able to provide GUI applications (and thus browsers by extension). But I’m glad to hear that it has provided you a decent experience so far!
My only experience with homebrew is on macOS and I’ve switched to MacPorts there. Homebrew did some weird permissions things I didn’t care for (chowned all of /usr/local to $USER, if I’m remembering right). It worked fine on a single user system, but seemed like a bad philosophy to me. This was years ago and I don’t know how it behaves on Linux.
I also prefer Firefox, but when I need a Chromium alternative for testing, I opt for the flatpak (or the snap) version personally.
Based on what I saw on macOS I wouldn’t touch Homebrew with a 10 feet pole. We have proper packaging systems in the Linux world. The Chromium snap is supported by Canonical so that’s a great candidate for anything that comes with snap or can use snap. If I couldn’t use snap, I’d use the Chromium flatpak from Flathub.
Based on what I saw on macOS I wouldn’t touch Homebrew with a 10 feet pole. We have proper packaging systems in the Linux world.
Could you please elaborate on how the packaging in the Linux world is better? I can imagine why, but I’d rather have a better-informed idea on the matter. Thanks for your input!
The Chromium snap is supported by Canonical so that’s a great candidate for anything that comes with snap or can use snap. If I couldn’t use snap, I’d use the Chromium flatpak from Flathub.
I use Chromium from my repo already, but as stated in the OP; I would switch in an instance to Brave if I could.
I use a few packages from Homebrew and don’t have any problems with it. By default it installs itself into /home/homebrew or something which I didn’t like so I put it into ~/Applications/Homebrew instead using these steps. It warns that you may be forced to compile software if you do it this way but I’m down to clown so whatever.
The biggest problem I have with it is that you’ll need to keep it updated alongside your regular packages, which I do by aliasing a simple upgrade command that runs all my package manager upgrades.
I would also recommend ungoogled-chromium as an alternative to Brave, which does have its own official Flatpak (not marked as such but it’s linked to in the ungoogled-chromium project github).
Well, you can’t blame developers to not cater to their 1% player base. Especially since that group usually have the most problems and requires more development time.
The rust one is called bottom (btm) see the other thread :). When you already have a rust environment it is just at a cargo install away which is convenient.
Just found this too, through the rust post some days ago…but its quite obvious that from a usability context that btop is easier to use. With bottom you have to memorize all hotkeys wheres btop is showing them right in the interface.
Yea. I was using bottom until I saw this and did a quick side-by-side comparison (nix-shell -p btop, I use NixOS BTW). btop’s UI is just so much better.
That part is stupid indeed. If you run X, do xinput and find your trackpad. Then do xinput list-props on that to see all the settings there are. Xinput can also change them with xinput set-prop and they reset after a reboot, so feel free to fiddle around.
Once you’re done, just slap your settings into a script and run that on startup, then you’re set.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.