Forum Discussion
Google Earth also not supported in Edge Canary
, the Google Earth normal ver however is still not working. Google hasn't backed off from their stupid Edge blockade yet.
HotCakeX "Yup, Google Earth beta is working with Edge Version 77.0.218.0 (Official build) canary (64-bit), the Google Earth normal ver however is still not working. Google hasn't backed off from their stupid Edge blockade yet."
Although I despise Google, I don't think that it is a matter of Google blockading Edge Chromium.
The Google Earth beta uses WebAssembly, which modern browsers (e.g. Edge Chromium and Firefox) support, while the "normal" (that is, current production) version of Google Earth uses PNaCl, which is a depreciated, legacy technology that is not supported by Edge Chromium, Firefox or most other modern browsers.
All is not entirely well in the Google Earth world, however. WebAssembly is designed to be multi-threaded, enabled by SharedArrayBuffer (SAB), which was disabled in most browsers in the wake of the Spectre and Meltdown vulnerabilities. Google Chrome uses uses SAB, but also uses site isolation to mitigate the risks. Other browsers (Firefox, for example) disable SAB, and Google Earth beta does not multi-thread in those browsers. I don't know how Edge Chromium deals with this issue.
I think that is is important to keep in mind that the Google Earth beta is (in the words of Google) "an experimental version" that is not yet fully functional. We'll see what happens going forward.
As a side note, opening the Google Earth beta in EdgeHTML (Edge Classic) gets this:
I don't know, but I'm thinking that this is probably related to the SAB issue.
i don't know about your story...as nastyaaelisya mentioned, earth only checks for user agent, not browser capability. that's shady af
HotCakeX "i don't know about your story..."
I have no idea what that means, but the fact is that the "normal" (that is, current production) version of Google Earth for browsers uses PNaCl and the Google Earth beta uses WebAssembly. Google Earth for browsers does not run on mainstream modern browsers (e.g. EdgeHTML or Firefox), period, because modern mainstream browsers don't support PNaCl,
"earth only checks for user agent, not browser capability"
That may be, but since the current production version of Google Earth doesn't run on any mainstream browser other than Google Chrome (the only mainstream browser currently supporting PNaCl), checking the UA to see if the browser is Chrome (and not anything else) seems an efficient way to block users whose browsers won't run Google Earth before the browser tries to open Google Earth and crashes.
I have low opinion of Google. The whole Google ecosystem is an intrusive data-mining operation. I don't use Google products or services (Chrome, Gmail, Docs, Earth, YouTube, etc.) unless I have absolutely no alternative, either in the Windows environment or in the Linux environment. In short, I'm not a Google fan, and I think that users who uses Google products and services are opening themselves up for invasion of privacy. But in this specific instance, I don't think that Google is up to anything.
one more thing, i havent respond with tat yesterday since i haven't find it but : https://www.ghacks.net/2017/04/18/google-makes-the-new-google-earth-chrome-exclusive/
or
https://www.ghacks.net/2019/07/15/firefox-68-aboutcompat-launches/
Firefox have to add some functionnality to bypass the google's politics of systematic bloquation of other browser than chrome
- Even if you changed the user agent, Google Earth still wouldn't work with non-Chrome browsers. Google Earth currently uses NaCl as I mentioned in my other reply. It uses wasm in beta. There are lots of wasm flags in Chrome/Chromium/Edge. If you want to show your support, enable it and use the beta! :3
Deleted Google does many scummy things but this ain't one of them. Just try changing your user agent via an extension and the production version still won't work.- it's maybe the case here (i have not tested) but when you saw on google website or another "website optimized for google chrome" it's a bull**bleep**, they tested it on chrome but not "optimized it".
Or simply the message "hey our services work's better in chrome" bull **bleep** as well.
For me google has lied so much about it that now it's lying by default unless evidence to the contrary.
