Forum Discussion
Google Earth also not supported in Edge Canary
I think it has to do with Google's proprietary Native Client. WebAssembly is the standard.
I'm not even sure what WebAssembly and Native Client *actually do* but I know it has to do with performance.
Edit: I did a quick search. https://news.ycombinator.com/item?id=18677689
"It looks like they are waiting on WebAssembly Threading. I agree with you though, Google should help develop WebAssembly vs just creating a Chrome only solution:
"Our 3D rendering engine currently uses a Chrome-only technology called Native Client to power Earth Studio. However, we’re closely tracking the evolution of WebAssembly (especially threading). Stay tuned!""
"> Google should help develop WebAssembly vs just creating a Chrome only solution
"> Google should help develop WebAssembly
Google is heavily involved in WebAssembly planning and implementation in Chrome/V8. They have threading enabled chrome://flags"
From these three comments I feel like Google is at fault. I'm really happy that a quick search lead to so much information! :)
The people who can do Google Earth Flybys might not be the same that could implement WebAssembly Threading, even though they work at the same company."