• 0 Posts
  • 38 Comments
Joined 9 months ago
cake
Cake day: June 23rd, 2024

help-circle

  • I don’t think his statement is true though. If https://www.reddit.com/r/linux_gaming/comments/1ce7z19/gaming_on_linux_ep131_ntsync_vs_fsync_nobara_39/l1ho8od/ is not manipulated in any way, games with lots of these calls still get big improvements with ntsync over fsync (about 30% in this particular case, which is a massive boost). So while nobody can rule out that his statement may be true on average or in general, there are still cases where ntsync offers a tangible advantage – be it improved FPS or the fact that the game runs at all.

    Edit: in the video that the thread is about, fsync didn’t beat ntsync in a single one (or I missed it when jumping through it). In the best one, they were exactly tied. Sure, the difference wasn’t really big, but again there are titles not working with fsync.

    However, I want to stress that I’m not trying to talk about fsync. It’s a good solution that significantly improved performance. But ntsync is, from everything I’ve seen, almost always better; how much depends on the case, and it never seems to be worse.









  • the average package quality is currently closer to that of the AUR than the official repos of other distros.

    Care to elaborate? I don’t remember packages not working, but if anything, they’re not building; which is basically the reverse of what happens at other distributions where sometimes, breakage during building isn’t noticed because the packages aren’t getting rebuilt when a dependency or the compiler toolchain changes.




  • True! My original point though is that just providing a hash for a downloaded file is generally not required. It doesn’t provide anything that other layers haven’t already (a hash only guarantees integrity, while downloading over HTTPS provides authenticity). Personally, I see them as a relic of the past that made more sense when transmission was less robust (though even back then, a lot of layers provided some sort of error detection and correction), and modern filesystems can detect errors as well.








  • While still not correct with that in mind, the “initially” refers to a sound server a that sits above ALSA. There were others before Pulse, for example the aRts daemon and ESD. However, these were mostly used within their respective Desktop Environment while the rest used ALSA directly, so Pulse being the first Sound Server being widely used under Linux is one way to look at it. JACK on the other hand never left the (semi)professional niche I think.

    In fairness to Pulse, Pipewire built heavily on its foundation; in fact, is initially was only supposed to be “Pulseaudio for video”, and Pulse led to huge improvements in ALSA and audio drivers. Pipewire simply couldn’t have worked as well back then as it does today if it had been released when Pulse was initially.