I agree. There is literally 0 reason to buy anything from Apple when there are much better and much cheaper options that are already well supported by GNU/Linux. I will never understand people who will go out of their way to waste money on the next big thing from Apple only to get Linux on it.

It doesn’t help that they keep deprecating and changing standard stuff every other version. It’s like they can’t make up their mind and everything may be subject to change. Updating to the most recent release can suddenly cause 10s or 100s of compiler warnings/errors and things may no longer behave the same. Then you look up the new documentation and realize that you have to refactor a large part of the codebase because the “new way” is for whatever reason vastly different.

On distros w/o systemd there is always syslog-ng. s6 also has its own log system.

It’s not necessary, but a good thing to have if something goes wrong and you want to debug/monitor something. It’s really up to you and your needs.

https://github.com/phkaeser/wlmaker

Gallium-Nine also tends to be buggy if used with 32-bit software in particular. All the 32-bit games I’ve tried have problems with it. They usually work fine for the first 30-60 minutes and after that the framerate becomes unstable to the point where the game becomes unplayable. It happens consistently with Gallium-nine but not at all with DXVK.

I have the same experience. I wrote a simple program with SDL2 to test a software renderer. All it does is create a window then go into an event loop and after each iteration it streams a framebuffer to a texture that gets displayed in the window. In the default mode (X11) my frame timings fluctuate a lot and for a while I tried to massage the code to get it stable because I was convinced that it was just my draw code. Then I eventually forced SDL2 to use Wayland and not only did the draw time per frame go down by 2ms but the fluctuations went away completely.

Kepler cards work “OK” with nouveau. What sucks is that reclocking has to be done manually, video decoding/encoding requires firmware blobs and OpenGL support tends to be meh. Overall it’s an unstable experience. I have a stack of Kepler based cards that would still be usable if Linux/mesa had a decent driver.

Firefox does sandbox everything but vulnerabilities exist and sometimes go unnoticed for a while before they’re discovered and patched. If a malicious script does manage to escape the sandbox it will be able to do literally anything to the system since it has root privileges. It would have full access to any device that’s in /dev, it could create, modify and delete udev or iptables rules, it could mess with the BIOS since the kernel exposes EFI variables, if the mainboard has re-writable flash chips for the firmware it could write malicious code to them since they may show up in /dev, etc. If any of this makes you uneasy then you probably should stop running stuff as root in general except for when you really need to.

Also in general you don’t want to run any graphical applications on a Server unless there is a very specific reason for it because it takes up extra resources and therefore makes the machine use more power overall. This is especially bad when the machine in question has no hardware acceleration and renders everything in software. Remote desktop also adds CPU/GPU load and takes up a good bit of I/O and network bandwidth which is not ideal for a NAS server.

lact

Anyone that thinks X11 is still superior probably runs on a laptop with a single screen.

It really does seem that way. I’ve dealt with many different multi-monitor setups on X11 and only ever had problems. For example, I have an AMD based setup with 3 monitors, 2 are average 1080p60 displays and the third has a higher refresh rate. On X11 this setup always has either screen tearing/flickering, unusually high CPU usage by the compositor or the refresh rate seems noticeably off and hot-plugging additional monitors makes things behave weird or even crash, especially when unplugging monitors. On setups with multiple monitors across multiple GPUs it’s the same but worse. On Wayland it all just works without any problems, no matter the setup. Hot-plugging monitors on Wayland is very seamless. Even X11 software runs better for me on Wayland.

I agree. The proxy solution they’re proposing seems like a band-aid on a fundamental design issue to me. It’s easier to just tack yet another library onto a big project than to refactor large amounts of code. This is exactly why a lot of software is getting more and more shit.

I remember this. I refunded the game ASAP. For the longest time they’ve neglected the Linux client to the point where it was just broken and crashed often and you couldn’t even play with Windows players because the Linux client was so far behind. And of course the Windows version ran just fine on Linux via Proton. Yet they seemed surprised and annoyed whenever Linux players pointed this out. That’s where I lost all my respect for them as a developer. I would refund Gary’s Mod too if I could.

Similar but in this case the Linux Kernel/Init System act as the PXE firmware so you don’t need a TFTP Server to load initramfs and a Kernel image. And you don’t need a NFS or Samba server because the Server has the drive with the rootfs already exposed to the network.

From what I understand it’s basically like a “thin client” type of thing where the client loads the Kernel from local storage up to a certain point and then boots into a rootfs that is somewhere else on a remote server.