21–30 of 78 posts
Earlier quoted context omitted.
Don't most people use chromium instead of chrome anyways on Linux?
most people just click the "internet" button and use whatever was already pre-installed.
Looking forward to no longer having to patch glibc on my Linux phone just so I can watch YouTube or use Spotify.
Wait what, how is glibc patching related to YouTube and Spotify? Could you not watch YouTube using an arm64 build of Chromium or Firefox?
Same thing with YouTube. A few months ago, YouTube started to require Widevine CDM if one uses the m.youtube.com site. I can't use the non-mobile site on my phone for performance issues, so I'm essentially locked into Widevine for watching YouTube, too.
Wait... weren't there many ARM Chromebooks already?
All of that is very different from The G actually providing a packaged official Chrome build, though. Which for some reason they couldn't be bothered to do before (Firefox exists though)
Sorry, Google. Too late!
(Bonus: ad blocking properly works).
Earlier quoted context omitted.
Wait what, how is glibc patching related to YouTube and Spotify? Could you not watch YouTube using an arm64 build of Chromium or Firefox?
Spotify requires Widevine CDM to run, and Firefox doesn't come with Widevine on Debian-based distros. The .so hasn't been available on arm64 except for ChromeOS. You can rip the .so out of ChromeOS (that's what RaspberryPi OS did). But ChromeOS uses its own flavor of libc so a couple of patches to glibc are required. Same thing with YouTube. A few months ago, YouTube started to require Widevine CDM if one uses the m.…
I guess it must be a snap, not a deb package, but... wouldn't that work?
I recently switched to using an NVIDIA Spark as my primary workstation and lack of Chrome binaries for it are what finally pushed me to completely sever my relationship with Chrome and switch to Firefox. Sorry, Google. Too late! (Bonus: ad blocking properly works).
I have been waiting... so many years for this. Like, I figured it would never come. So happy to be wrong. Wonder if it will work well on Raspberry Pi and also if it will come with Hardware Video Acceleration out of the box.
I would have more faith in Raspberry Pi's own patched build of Chromium to do hardware acceleration properly on the Pi than I would have in Google's generic Chrome build.