You either come up with something like frog-protocols to try and actually get things done, or you can wait for Wayland devs to endlessly bikeshed. Getting some amount of harmless fragmentation on an open source project seems much better than waiting 4 years (and counting) for them to start actually working on implementing HDR.

ToS and EULAs are generally not at all enforceable in most of the world

In the real world with real people, what matters is efficiency. Top performance that you can only achieve in benchmarks is not any indicative of efficiency.

Yes, and that’s the reason Google is abandoning it since they can’t profit off of it.

Like the other commenter said, Google is actively dropping support for JXL in favour of their own WebP, and despite it performing worse than JXL in every single test, JXL doesn’t pay royalties to Google.

Explain to me what would be the good reasons McDonald’s has to block their app from running on a rooted device because it doesn’t pass SafetyNet or whatever Google is calling it now

Take a look at FUTO: https://keyboard.futo.org/

“unrivaled in quality”

Are we forgetting the countless issues the Nexus phones had? The 5 for instance had bad camera quality and battery life even for the time, the speaker was as loud as a whisper, the side buttons would stick with less then a year of usage…

Probably not, as the image says Zen is based on the latest Firefox and Floorp isn’t.

People would still be talking about it if it were a flop, nonetheless this game has sold almost 2.5 million copies on Steam alone, far from being a flop.

Well but that still depends on Google adding that functionality, which can be anytime between now and never

Doesn’t it depend entirely on FMD network? If so, then it shouldn’t work better or worse than the other options since they all use the same restricted Google network

This doesn’t change anything, Google said 7 years of OS updates, not 7 Android versions. The device should be getting support until 2031 regardless of which android version it shipped with

I really can’t explain but I type WAY worse on HelBoard. I’m usually quite accurate typing on phones, but on HeliBoard it’s almost as if my finger is always shifted to the side, and that every tap has twice the delay

The guy in the thumbnail (Fernando Haddad, Brazil) has been very effectively taxing everyone except the rich and super rich. The super rich got annoyed that people were buying things from China instead of their resale so he decided to intervene by forcing an import tax of 60% + state tax (between 10% and 20%) over every imported product. Of course, the rich importing these same products to resell on a hefty price increase pay 0 taxes because “they’re protecting the national industry”.

Creating ads that are even more targeted to you so you can forget about everything and buy that electric kitchen knife you just saw scrolling reddit

Zed is not an IDE, it’s a code editor. No, they aren’t the same things, it’s like saying a table and a kitchen are the same thing.

Wouldn’t running it on privileged mode cancel out whichever safety measures of running that script in a container?

Running endeavourOS with a 3080 and Plasma since 5.25 (on 6.1.2 now). Never ran x11 and I don’t intend to ever again. My experience is mixed, so to say. There are a few things keeping me on Windows but (very) slowly I’m getting there.

About HDR. I didn’t need to do anything extra to get it enabled on my desktop, simply toggling it on settings works.=, and I can also get mpv to work with some tweaks so I can watch films. On games I would need gamescope to run it, but that comes with a set of issues like not having Steam Overlay and Input, so for HDR games I run them on gamescope without overlay, and every other game I just run them normally. I also have a lengthy writeup on trying to get gamescope to run with the Steam overlay, but ultimately it’s one or the other right now.

On NVIDIA drivers, for me the 555 and explicit sync patches have made things worse. I never had issues with things flickering on 550 except for Electron apps, which would flicker and have awful input lag, but that’s easily fixed by setting ELECTRON_OZONE_PLATFORM_HINT=wayland on my /etc/environment. The issue with 555 drivers is that there are some VRAM leaks happening. They fill ridiculously fast, even just dragging a window will make kwin use 2GB of VRAM. Since there is no shared VRAM at all on NVIDIA Linux, as soon as I hit my 10GB cap, Xwayland will crash along my game and Steam, and sometimes my desktop too. On 550, I would only get framedrops for a while. I should also note that the proprietary and open drivers have no difference at all for me, and enabling or disabling GSP firmware also has no difference.

Lastly, VRR. It will not work at all if you have more than one monitor connected and enabled on your NVIDIA card. A workaround if you have a second GPU (or your CPU’s iGPU) is to plug your extra monitors there, and then VRR will work on your main screen. A second option would be to disable your extra monitors anytime you would play a game, but that’s not ideal at all.

USA users think Beeper was meant just for I message, so by dropping support for that, they “blew their wad”. On the contrary, Beeper is going even stronger now that they stopped messing with Apple’s antics.