





It depends on what you want to run.
Games generally run very well or even better than windows, but if your target is games you should use a more “optimized” verison of wine, like proton. Other applications are a bit of a hit or miss: things like MS office, adobe trash, etc. don’t run very well if at all, some may have random issues like crashes or the UI not working properly, others run perfectly, you have to try it.
If you run into issues, don’t be discouraged: for games, take a look at protondb.com or PCGW (fixes that work on windows usually work on wine too), for applications, check the appdb on winehq.org; when something doesn’t work more often than not it’s just a missing library or some setting you have to tweak.


I develop a similar tool and this thing is absolute slop: it’s full of obsolete settings like RADV_PERFTEST=gpl,rt (both have been unnecessary for years), broken features like FSR4 (it needs a DLL from the AMD drivers to work that this thing doesn’t provide), and anticheat support is a complete lie, none of that trash will ever work in wine.
Also, I don’t know why you would ever use a debian-based distro for gaming, the drivers are 6 months to 2 years out of date, you’re just asking for trouble.


The Eaton unit is a UPS that’s connected to the whole setup. It works really well, I can recommend it.


The home server under my desk. Very professional, as you can see.



Because in web development it is perfectly normal to use 2 frameworks and 1200 random libraries to do the simplest of things. One compromised library will compromise all applications that rely on it directly or indirectly, no matter how small.
I absolutely hate this aspect of web development and frankly I’m scared every time I type npm install
I absolutely love Kate, I’ve been using it since 2019 when I switched to Linux and I needed a replacement for Notepad++, and I prefer it to more sophisticated editors like VS Code.
deleted by creator


What can I say, I’m a sucker for punishment 😂
I like having the latest (or at least recent) hardware so having the latest kernel and mesa is a must.


Things have gotten A LOT better since I started using it, but here’s a list of things I hate after using Arch with KDE as my main OS for almost 7 years:


I donate 100€ to KDE every year. I consider it my “windows license”, since it was the DE that allowed me to escape from windows 7 years ago.
If I had to guess, the second curve allows the GPU to boost higher than the first one, so it generates more heat.


Alright, I’ll get a zigbee dongle then.
Thanks for the replies.


This sounds similar to one of my projects that could use some extra love: https://github.com/adolfintel/tdf
Personally I had zero issues with upgrading my server to Debian 13; it’s an installation dating back to Debian 9 or 10 with a lot of services installed.
The only inconvenience I had was that somehow Transmission 4.1.0 beta made it into debian stable, and beta clients are usually not allowed by private trackers. I switched to deluge and called it a day.
I’d love to see more studios make puzzle-adventure games, like the ones by Cyan


It would need to be open source, distributing proprietary kernel modules is a nightmare that can cause the OS to fail to boot after every kernel update. An open source anticheat kernel module would probably be useless and easy to bypass.


It actually happened to me today on Arch.
I updated the system, including the kernel, everything went smoothly with no errors or warnings, I rebooted, and it said the ZSTD image created by mkinitcpio was corrupt and it failed to boot.
I booted the arch install iso, chrooted into my installation and reinstalled the linux package, rebooted, and it worked again.
I have no explanation, this is on a perfectly working laptop with a high end SSD, no errors in memtest, not overclocked, and I’ve been using this Arch install for over a year.
The chances of the package being corrupt when I downloaded it and the hash still being correct are astronomically low, the chances of a cosmic ray hitting the RAM at just the right time are probably just as low, the fact that mkinitcpio doesn’t verify the images that it creates is shocking, the whole thing would have been avoided on an immutable distro with A/B partitions.


Generally speaking, Linux needs better binary compatibility.
Currently, if you compile something, it’s usually dynamically linked against dozens of libraries that are present on your system, but if you give the executable to someone else with a different distro, they may not have those libraries or their version may be too old or incompatible.
Statically linking programs is often impossible and generally discouraged, making software distribution a nightmare. Flatpak and similar systems made things easier, but it’s such a crap solution and basically involves having an entire separate OS installed in parallel, with its own problems like having a version of Mesa that’s too old for a new GPU and stuff like that. Applications must be able to be packaged with everything they need with them, there is no reason for dynamic linking to be so important in Linux these days.
I’m not in favor of proprietary software, but better binary compatibility is a necessity for Linux to succeed, and I’m saying this as someone who’s been using Linux for over a decade and who refuses to install any proprietary software. Sometimes I find myself using apps and games in Wine even when a native version is available just to avoid the hassle of having to find and probably compile libobsoletecrap-5.so


I’d say I’m a “time-strapped” user since I have a full time job and I’d rather spend my free time gaming rather than fixing a broken OS, nevertheless… I have 2 PCs with Arch Linux (one for personal stuff and one for work) and a server with NixOS.
When things break on Arch (which is rare these days but it can happen, especially if you play around with things from the AUR), I just rollback with timeshift (it takes just a few seconds with btrfs) and try that update again in a few days. Minor issues I can just ignore or work around them and take care of them when I feel like it, but they usually get fixed with updates within a few days. The only time I felt that it was actively wasting my time was when Plasma 6 came out a few months ago and a lot of little things broke, especially on wayland, but they were fixed rather quickly with 6.1 so I can’t complain too much.
NixOS on the other end has been nothing but trouble and a waste of time ever since I installed it. It took me a week to configure it, some packages are kinda old, most have incomplete declarative config, I had to manually write some units myself, and when things break it drives me crazy because even basic troubleshooting of services can be a pain in the ass because I have to find out where stuff is, know which config files are going to be overwritten, launch the correct nix-shell, … it’s all so tiresome… so I just revert to an older config and hope for the best. To make things worse, major updates often require manual changes to the config or even to application files themselves (looking at you, nextcloud) and you will excuse me if I can’t be bothered to do that on a DECLARATIVE DISTRO. Even debian doesn’t need that, come on! I don’t care what people say on NixOS, this OS is not ready yet, I don’t have time for this shit when I’m working and that server will be going back to debian next summer.