@throws_lemy @IchNichtenLichten
There's really not much "outer" to Windows's limits.
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.
@lanigerous @Spendrill It's also very conductive. It's not an accident that gold is used in high-quality electronic contacts like cable ends or card edges.
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.
Wayland might be nice for those who use major desktop environments, but I prefer the Awesome window manager. Unfortunately, this is not available in Wayland, and there's nothing in Wayland that meets all the features I am used to. 😞
Additionally, when using Wayland, screen capture utilities like flameshot or shutter won't work until you first take a screenshot using Wayland. It's kinda frustrating.
@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.
@originalucifer @ozoned @itmike
It's not that difficult to describe. The media is described based on its content, format, and time of release.
If the core content is text-based, it's a blog. If it's audio-based, it's a podcast. If it's video-based, it's a either a vlog (for personal content) or simply video (for topical content). These all assume the content was first created, and then released.
If it's released at the time it's produced, it's a livestream, or just a stream.