Well, freedesktop.org is now focused on Wayland (Xorg is not getting HDR, new synchronization protocols, or proper VRR (unless through XWayland), while Wayland is). RedHat RHEL marked Xorg as deprecated last year and will not even support it by next year (RHEL 10). KDE and GNOME also default to Wayland.
He says while using WIFI, phone calls, GPS, and who knows what else every single day.
You can’t escape US Sanctions, no matter what you choose. So it’s whatever.
Ok, lots of Russian trolls out and about.
It’s entirely clear why the change was done, it’s not getting reverted, and using multiple random anonymous accounts to try to “grass root” it by Russian troll factories isn’t going to change anything.
And FYI for the actual innocent bystanders who aren’t troll farm accounts - the “various compliance requirements” are not just a US thing.
If you haven’t heard of Russian sanctions yet, you should try to read the news some day. And by “news”, I don’t mean Russian state-sponsored spam.
As to sending me a revert patch - please use whatever mush you call brains. I’m Finnish. Did you think I’d be *supporting* Russian aggression? Apparently it’s not just lack of real news, it’s lack of history knowledge too.
Actually insane lol. But you can’t expect much from anybody who willingly takes money from IBM.
Sure. Until that happens, it will be the better option.
And in terms of cashflow, they depend on that google money. They’re in trouble without it
That’s irrelevant. The only thing important is what they have to do for that money, which is setting Google as the default search engine. This only “hurts” you if you don’t take 15 seconds to change the default.
How are they doing that? They’re simply making money by putting Google search as the default. Changing it literally takes a few seconds.
Yes. The Google-funded Firefox that won’t take away your ability to block ads. Any other questions?
That’s not what this is about. He’s complaining about hardware developers putting more work on kernel developers by making them patch all the CPU vulnerabilities that are introduced by trying to increase performance.
In an ideal world the headline would be “Google kills Chrome by preventing users from blocking ads”.
FSR is an AMD technology and it’s not AMD exclusive. So one doesn’t imply the other.
This isn’t really driver related. It is the Wayland compositor’s job to properly handle multiple GPUs, which is lacking in some (a very popular, Wayland library that lacks proper multi-GPU support is wlroots) compositors. Vulkan drivers and DRM are already enough to properly handle multiple GPUs. I guess Wayland implementers just haven’t cared enough about the issue, or maybe are figuring out a “perfect” way to address it (a la 3 year long pull request on wayland-protocols repo incoming)
Doubt it’s a sway problem. You got it to work with waybar in plasma, or just in a terminal? Anyways, my setup is also sway+waybar so I’ll try to use cava later today.
They’re so done with NVIDIA they don’t even have the energy to attack them on a forum anymore
Interesting. Well it was worth trying I guess.
Try increasing the height of the bar to some insane value. Just to make sure it’s not cava being unable to scale down.
https://github.com/audacity/audacity/wiki/Roadmap
They’re only waiting for some code restructuring to release 4.0, which includes UI rework.