SGH

Yep. There’s no AUR for bazzite since it’s based on fedora immutable, unless I’m mistaken and there’s a way to do so anyway somehow. Still, bazzite and AUR do not go hand in hand AFAIK as it’s meant to be an immutable system.

Just to not sound like a complete asshole… ofc the 25% boost does not depend on bits/kbits, the difference is still 256 vs 320, but I just wanted to emphasize that the expected result is 25% bigger in all terms.

If it helps to imagine, the space needed to store a 256k 5 minutes song will store a 320k 4 minutes song. Then, you are already relying on a quite decent quality beforehand so it’s all extra quality and details.

I usually hear the difference in the high frequency sounds, which is exactly what is otherwise sacrificed in low bitrate compression formats.

FLAC will produce an even better sound, as it’s lossless, but for most songs I couldn’t justify the file size difference.

That’s 64 kbits, or about a 25% boost in bitrate.

Not a lemmy user to my knowledge, but for a while I kept finding various social media accounts for a specific user.

They were (maybe still are? No clue) a very active and knowledged user of cplusplus.com, and we had some mild interactions over time.

Eventually, for some unknown reasons I got suggested its YouTube channel with some Minecraft videos, its GitHub account, and I found some comments of theirs on some Reddit threads here and there.

They now work for a software development house of a relatively obscure product that I have used before.

It’s just the fact that, at some point, if you want a faster computer, you’re bound to have DDR5.

AMD 5000 is fast, but how does it compare to last gen? Is there a 5000 CPU that can get the same score as a high end 9000 CPU?

What if you have a homelab server to upgrade but find out you need more PCIe lanes?

Other than that, yeah, you don’t need DDR5, but DDR4 is slowly going out of production and is also rising in price… so you’re screwed either way.

It only depends whether the app and its OS/kernel interface use a 32-bit value to store the time information.

32-bit architecture or OS has nothing to do with this bug, for example 16-bit architectures must’ve used 32-bit time, too (otherwise they’d be able to only count up to 32-65 seconds).