Exactly what I expect from the latest Debian. Boring and not working. Too many hacks by people who cannot work with upstream and have no idea what they are doing. But they are having their own good idea of a "proper" layout and package management.
Curious what you run, instead of Debian. I haven't had the same experience as you've had, but for myself, Debian has just worked other than having to provide my own wireless adapter driver .so file when I installed off a thumb drive without an Ethernet connection. While I have more experience than the average Linux user, and got started with Slackware in the 90's and then moved to Red Hat in the very late 90's, it's been a good 20 years since I used a Linux system full time. That's as a desktop, I've had no issues running as an application server for 2 decades.
I haven't run into a scenario where the desktop has caused me issues, only with Windows-only software that I sometimes require. What software has caused you issues that doesn't play nicely with Debian? What hacks are in place to mitigate upstream issues? I'm honestly curious, and if you don't use Debian, what distribution do you use regularly?
It's Debian testing; a rough experience is practically expected. I say this as a person who daily-drives Sid.
That's some hyperbole. If I spent 6 hours a day fixing some distro's issues, that would be my whole job. I would begin questioning whether I'm "holding it wrong" or if it is the wrong tool for the job.
That's an opinion (a wrong one IMO, but you do you). It's hard for me to comment because when I tried using Fedora (maybe 15 years ago, tbh) I couldn't even play MP3s out of the box, so I never revisited it.
I also left Ubuntu because of their shenanigans, but if your code cannot run on Debian, your code is shit.
When the python3.10 package has the SSIZE_CLEAN error enforced, and one of their packages has no SSIZE_CLEAN definition before including Python.h (python3-bluez) that's not my fault. That's just yesterday's shenanigans.
