There’s nothing to prevent data races. I myself have fallen into the trap of using the same list from multiple threads.

There’s a difference between source available and open source. For example, actually being allowed to distribute modified versions is pretty damn important:

Restrictions

• No Distribution of Modified Versions: You may not distribute modified versions of the software, whether in source or binary form.
• No Forking: You may not create, maintain, or distribute a forked version of the software.
• Official Distribution: Only the maintainers of the official repository are allowed to distribute the software and its modifications.

I mean, Swift is not an Apple project just like .NET is not a Microsoft project - barely. I have not heard of significant outside involvement in either of them.

At least a while back there was not a built-in GC on the WASM runtime side, so the GC has to be shipped with every app.

Make sure that port forwarding is actually working - on ProtonVPN the port allocated to you can change regularly and QBittorent’s settings need to be updated accordingly. Easiest way to check is to click through your active torrents and check if any peer has the I (incoming) flag.

If you have not set up something like this, port forwarding is probably not working: https://github.com/mjmeli/qbittorrent-port-forward-gluetun-server

I would personally just run the plain script as a cronjob on the host though, to not rely on some random docker image.

Hmm, I might try to make that. Any particular feature you are looking for, or is just displaying all the events in a table good 'nuff?

The MSYS2 environment on Windows uses pacman as well.

No way they will ever be in sync.

Some distros have editions with a WM (usually i3) as a default, yes. These editions tend to come with some basic config so it’s more usable out of the box. But you can also install WMs side by side with DEs and then switch in the login manager (GDM, SDDM), just the same as you can install multiple DEs on a system. You could also install a headless version of a distro first and then install only the WM and whatever other tools you want on top of that. Basically all system settings can be changed through config files or CLI programs, for some things like audio and bluetooth there are good DE-independent settings programs like pavucontrol.

You can also replace the WM built into KDE (kwin) with i3, for example, but that’s pretty messy, IMO.

As for advantages, WMs are usually very keyboard driven, you pretty much never have to touch the mouse. They also tend to be fairly light weight and use little RAM. My favourite i3 feature is that workspaces are per-monitor, so I could easily move multiple windows between monitors and not lose the way they are set up.

As for disadvantages, changing any system settings tends to be a research project, because there is no centralized solution, it’s even worse than Windows in this regard. Personally this is the main reason I switched back to KDE from i3. I could also never get theming to work quite right.

WMs typically do not include stuff like a custom GUI for system settings and do not have a suite of GUI software associated with it (think Kate, Konsole, Dolphin etc) - it is just a piece of software for managing windows, you have to put the rest of the desktop together yourself.

It’s fine with the beta driver, so still not fine by default.

I’ve seen enough blurry software on Windows to know this is not quite true 😅

Native games need to add client side decorations to be usable on Wayland Gnome. Currently most games just run in XWayland.

The way I see it, GTK is really a framework for building cross-platform GUI apps. Then handling display server compatibility makes perfect sense to me.

If this was meant to be a dig at Wayland, I’m pretty sure GTK also needs explicit and direct support for X11, Windows and MacOS. It just already exists.

I’m pretty sure Louis is just another recipient of FUTO’s funding, not “the” other partner to this dude.

The flipside of this is that you as the BDFL are not in any way entitled to community contributions. If they decide to not like your furry board, they are free to fork the project, but splitting the development efforts could very well kill both projects, so sometimes it is better for the project to listen to the community.

Maybe the kernel version on Debian lacks hardware support fixes?

I saw a comment from an nvidia dev somewhere that XWayland support is enough to resolve the flickering, but compositor support is needed for best performance.

Maybe if your games are Wayland native or you’re still running the 535 driver? I saw fbdev=1 as a workaround, but that made things very jello-y.

Desktop 1660S