Just some goof who thinks he’s important. Ignore him, maybe he’ll go away.
It’s very attractive, but it also seems to have a minimum window size requirement that exceeds the “stack” in my “master and stack.”
It’s great to use if you need a dashboard to track issues, but for a quick look at running processes, I think I’ll stick with htop.
I should also probably mention that messing with the USE flags can make things a little brittle, since it’s possible to flag out options that might not be important now, but could become important later. Most binary distributions make things as flexible as possible to accommodate future changes.
I’ve used both, and really, from an understanding standpoint, there’s really not much difference between Arch and Gentoo.
Gentoo’s main advantage are its USE flags, which the packages use to determine which “configure” options to select at compile time. However, installing and updating the system can take hours or days while you wait for everything to compile.
Arch, on the other hand, uses binary packages, which is faster, but lacks the flexibility of USE flags.
@kevincox For light tasks, I will make use of either vterm (if I’m in Emacs) or Alacritty (if I’m not).
If I need to get down to serious work (such as working on shells and text files both locally and remotely), I’ll jump into eshell, using TRAMP when I need to go remote or sudo (or both) to edit files. I’ll still use vterm if I need something that does screen redrawing, such as apt.
For Steam, there’s not much of a question; they have a native app that gets the job done.
For Epic and Gog, Heroic makes a good launcher in general.
For Amazon games, I use the “nile” launcher.
As for EA, I’ve managed to install the EA App manually to a fresh 64-bit prefix; I just made sure that I run “winetricks d3dcompiler_47” in that prefix, and that DXVK is installed.
@throws_lemy @IchNichtenLichten
There’s really not much “outer” to Windows’s limits.