Yep, especially on a slow machine, it can be very noticeable.
Although I think I remember reading about some dnf optimizations that can be applied to help the slowness.
I'm using Arch simply because of familiarity and comfort in using it. That and pacman being fast usually helps me make up my mind whenever I try something else. I really hadn't experienced any major breakage in any of the packages in the standard repos, especially if everything is configured correctly. So I don't really have anything to say against Arch's stability.
I also hear good things about Tumbleweed, so that could be an alternative and more complete out-of-box package, but that also highly depends on how comfortable you'll be with openSUSE's way of doing things.
It all boils down to how you prefer to configure and manage your system and its packages, really. Nothing much more than that. As long it does the job, it's usually fine.
This combined with wefwef importing Apollo data makes it really easy to find the communities again.
Keeping a native OS UI design language for an app is very nice. Apollo was a great example of this!
I'd love to see Android's version of the same thing.
This is an interesting watch.
Thanks for sharing!
I used to use sound cards myself ages ago for MIDI and DirectSound acceleration. I didn't expect the hardware audio codecs to actually make a difference.
Nothing is stopping me from installing a PCIe Sound Blaster with a good old EMU chip. At least I hope so, the EMU10k1 and 20k1 have a hardware DMA bug which breaks them on systems with more than 2GB of memory lol
Not sure if I should go the CMedia route and just use Xonar instead. I do like Creative's features (especially ALchemy), but those you can gain on any machine using a software suite made by Creative themselves.
Are you serious?
Now you got me wondering why this is the case...
I wonder if it's just the drivers. Or something else, like the audio device name, or APOs.
Which game in particular did you have in mind?
Same here, experience got worse after upgrading the monitor.
I went from a somewhat matched pair of 1080p 75Hz monitors, one of which was ultrawide (2560 width) to upgrading my ultrawide to a 3440x1440 160hz panel.
That upgraded panel suffered every step of the way in Linux.
I absolutely cannot get 160Hz consistently if I have both monitors running. On KDE X11, compositor drops the rate to 75FPS to even things out (except the mouse lol). On KDE Wayland it works properly in this regard, but we all know how Wayland is on NVIDIA right now.
GNOME is a similar story as KDE Wayland, with an added bonus of stuttering.
I'm not losing hope, though. It's gonna catch up to AMD but man does it stink to use lol
The only other reason I really have to use X11 is because the hardware video decoding in the browser doesn't work in Wayland with NVIDIA. Most of the apps are actually becoming more and more stable.
You don't have to even use Windows. Even Ubuntu will do sometimes lol
xan1242
joined 1 year ago
The fountain of life