Earlier quoted context omitted.
Looks like the first hurdle is that it's relying on the deprecated document.registerElement API from an early draft of the Web Components specs, which prevents the app from booting in Firefox. Edit: Paul Kinlan reports that Earth is using PNaCl ( https://twitter.com/Paul_Kinlan/status/854351477506277378 ), which means it fundamentally can't run outside of Blink.
Just curious on why they would use PNaCl over WASM here? Wasn't WASM on track to becoming standard for native-speeds in the browser?
Google Earth Redesigned
221–230 of 292 posts
Re: Google Earth Redesigned
#222If any Googlers are reading this: What does the new Earth require that Firefox is missing? I'm happy to help file things in Bugzilla so that this Chrome App can grow into a standards-based Web app.
Re: Google Earth Redesigned
#223Earlier quoted context omitted.
It seems this is the Google way. They kill one product (especially a desktop product) and it takes years till the new one is on every feature on the same level as the old one... look at Picasa vs. Google Photos. Even today Picasa can do many more things that Google Photos cannot do today. I'm sure the native/old Google Earth has a ton of stuff which is not ported to the web version. Good they cannot convert Chrome it…
I find it interesting that they recently introduced location sharing to Google Maps as a new feature... which it had back in 2009, until they got rid of it.
Re: Google Earth Redesigned
#224"Google Chrome required" - sure, because current crop of web developers are too young to remember dark age of Internet Explorer domination.
Re: Google Earth Redesigned
#225Earlier quoted context omitted.
Looks like the first hurdle is that it's relying on the deprecated document.registerElement API from an early draft of the Web Components specs, which prevents the app from booting in Firefox. Edit: Paul Kinlan reports that Earth is using PNaCl ( https://twitter.com/Paul_Kinlan/status/854351477506277378 ), which means it fundamentally can't run outside of Blink.
Just curious on why they would use PNaCl over WASM here? Wasn't WASM on track to becoming standard for native-speeds in the browser?
Re: Google Earth Redesigned
#226Re: Google Earth Redesigned
#227They where knocking a large building down near the office recently, this has that building in a partial state of demolition and has modeled the girders that where exposed. I admit to looking at it slightly slack-jawed, that wasn't so much future shock as the future punching me square in the face. https://earth.google.com/web/@53.74539679,-0.32722384,18.713...
Re: Google Earth Redesigned
#228Earlier quoted context omitted.
They had tons of handy features in Google Maps before it was redesigned using Material Design. We used the route elevation data often to plan hiking trips with our parents to determine if they would be able to make a trek. The map scale was absent from the first couple releases and when they reintroduced it, it would only appear on zoom and then vanish. It took 3 or 4 more releases for them to finally add an option b…
If you'd like to plan trips that have elevation data, I highly recommend komoot.com. It uses OpenStreetMap, and is a great tool for planning hiking or cycling trips.
Re: Google Earth Redesigned
#229Earlier quoted context omitted.
It's not - they just stopped developing the desktop one because now they're all about web-only. It sucks too because we use the desktop one all the time at work - though we're slowly replacing it with custom Cesium-based stuff.
Do you think they will ever go back to building what people want?
Re: Google Earth Redesigned
#230Earlier quoted context omitted.
> What happened to the old rule of thumb People realized it's a stupid and impractical rule and ignored it.
>> People realized it's a stupid and impractical rule and ignored it. If by "people" you mean developers, and by "stupid and impractical" you mean inconvenient.
Developers realized that their rule was stupid and impractical (not just inconvenient, but actively impractical: async interaction is faster and requires js), and so ignored it.