Oh, I know this one! Make sure you’re using pipewire and use HDAJackRetask. You can reassign the ports to whatever, you can even swap mic and headphone if you want.

Something that annoys me about people who love to harp on about how bad Mozilla is because they’ve gone downhill (which they have): Who is better? Genuinely compare them to their competition. Google? Heck no. Brave? Nope. Microsoft? Absolutely not. Apple? No. People complain about how much Mozilla spends on advocacy, but then when they actually do the advocacy, they’re happy about it! They’re perpetually stuck between a rock and a hard place because they’re pulled in both directions and thus, Firefox suffers. But, are they actually a broken clock? Really?

I guess to be a little clearer: If you compare Mozilla to their past selves, they lose. If you compare Mozilla to anyone else in that space with the resources to develop a browser, they’re still the best of the bunch by a country mile.

This is literally on the road map for GIMP, right up top. (Status: no just means it hasn’t been started yet and isn’t planned for 3.2, not that it isn’t planned) https://developer.gimp.org/core/roadmap/

Yup. All of that is true. It also protects you from yourself by preventing you from making changes outside of the home directory so you can’t hose your system accidentally. It’s intentional.

I was thinking not only about the finicky drivers, but also the different audio backends, like ALSA and OSS, Pulse would have just come out at the time, so it was definitely getting better, but it was fresh off the presses back then, so it wasn’t good enough yet either. Nowadays, Pulse works pretty well, pipewire works pretty well, things more or less just work, Bluetooth can be a little weird, but usually you just need to change the settings on pulse/pipewire to your preference.

Audio and networking were a shitshow back then, nowadays almost everything just works on those two fronts. Also, having to edit your Xorg.conf is not what I’d call user friendly…