I don’t work on uBlock or even webdev but it doesn’t take much of a stretch to think YouTube’s servers will refuse to immediately transmit a video stream after the webpage is requested; probably waiting for a typical user to skip 2 30-sec ads.

I might be behind on the Tech News, but did Qualcomm really win the license dispute with ARM that quickly? Over the Nuvia/Oryon IP?

I wish I had a source but AFAIK it was planned, but MediaTek might be reconsidering, since Qualcomm’s X Elites haven’t exactly sold very well. Adoption is too slow.

I wish they put out Mini ITX boards or NUCs. I’d love to mess around with these SoCs in Linux.

Android Authority 's TL;DR (conveniently) doesn’t mention the actual downside to this update. But it’s fine imo, since this was actually a pretty insightful read.

My TL;DR:

• Google’s ARR/VRR implementation is hopefully more compatible with the GKI system vs. current per-vendor, per-device implementations
• To add this support, vendors must implement v3 of the Hardware Composer and Hardware Abstraction Layer APIs.
• That means also undoing existing kernel changes for their devices and retooling it to support HWC & HAL v3. Lots of engineering time.
• This solution still isnt perfect. There’s a notable limitation in something called the “panel’s Tearing Effect”, but im not an expert at displays so CTRL+F it for the paragraph in question.