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?

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)

Lol. It’ll work eventually.

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.