scp autocomplete be like

KDE, with breeze and a custom colour scheme. I find it less likely to lead to usability issues.

Ah yes, because linux drivers never break!

You might not understand the pain if you don’t own a tv tuner card but trust me, it’s ROUGH!

The stifling of innovation. So that’s more of a feature to microsoft

Linux has technical debt. The kernel only just stopped supporting the i386. I can’t imagine what patches upon patches were required to make the same code run on even 2 processors released 40 years apart, let alone every processor released in between.

Rebuilding the app for the newer version is an objectively better solution, because it allows you to take advantage to new features. 64-bit migrations are a game changer for example. But its an ungodly amount of effort. Every single sodding package has a person responsible for building it for every distro that supports it. Its only because its on the distros to make a given program work on their distro that the system works at all. I agree that I’d rather it be rebuilt to fit into the new system. But that’s a lot of work. Never forget that.

I’ll say it once, I’ll say it forever: Windows has better backward compatibility, period. Even compared to linux. Rebuilding an old open source linux app to work on a modern distro can be done, but it’s a process that could take hours or days. And if you don’t have the source code you’re shit out of luck. Have fun getting that binary built against a 1 year old version of glibc to work. This, incidentally is what things like flatpak, docker and ubuntu’s nonsense competitor to both (of which our hatred is entirely rational no really stop laughing) are trying to solve.

Meanwhile microsoft office still handles leap years wrong because it might break backwards compatibility with old documents. Binaries built for windows xp will usually just work on windows 11. Packages built for ubuntu 22.0 often won’t run on ubuntu 23.0. You never notice this because linux are a culture of recompilers. Rebuilding every last package once a month is just how some distros roll. But that’s not backwards compatibility, that’s ongoing maintenance.

• Fedora makes very minimal changes to downstream. The gnome experience on fedora is the experience the devs intended, for better or worse.
• It often experiments with new technologies. It was the first to ship pulseaudio out of box. And then again for pipewire. And if it wasn’t the first to install wayland by default, it probably was the first to stop shipping XOrg out of box.
• It doesn’t install snaps instead of native packages when you run rpm install
• It’s also Linus Torvald’s distro of choice if that’s worth anything

Oh come on, mesa is only (checks) 112 megabytes!

you know what, carry on!

If you’re going to shill a corpo distro, at least shill a decent one like fedora.

The only thing funnier than the linux kernel supporting a filesystem who’s creator murdered their wife, is people confusing it with bcachefs.

'the linux kernel might be removing a filesystem'
"you mean the one who's developer murdered his wife?"
'no the one who's developer keeps ignoring kernel mailing list protocol'

Glad to see it’s popularity is waning. Snap is the inferior universal package by many metrics and the steam snap in particular is very not ready for prime time.

You don’t comprehend just how easy it is to do GUI programming in Javascript. Like if C++ is a nunchuck and Bash is a cursed hammer and lisp is a shiv then when it comes to GUI programming Javascript is Vector’s control panel from dispicable me.

I hate electron apps. Just make a website asshole, don’t bundle a whole chrome browser! The only one I’ll tolerate is ferdium, because having a message control center is kinda neat.

especially as the hack flows downriver to distros with actual dignity like mint. Like this is pollution of the water supply dog!

well at least they aren’t trying to make me install snaps, and patching apt so if I sudo apt install firefox it installs the snap version.

libaom is a fucking joke. SVT might be a memory hog, but as the proud owner of a system with enough memory to run it, I can proudly say my 1 minute video rendered in less than ten minutes and somehow had worse compression than x264

Wait, whot?

If most BSDs are running on the likes of AWS and azure (which wouldn’t surprise me) then it could well be true

Less likely to get RTFM from people who remember what it’s like to love a computer not obsess over it I suppose

Even if you’re using debian 12 bookworm and are fully up to date, you’re still running [5.4.1].

The only debian version actually shipping the vulnerable version of the package was sid, and being a canary for this kind of thing is what sid is for, which it’s users know perfectly well.