Google Earth 5.0 Silently Changes Update Policy
mario_grgic writes "Recently announced Google Earth version 5.0 adds interesting new features like images of ocean floors and some detailed images of Mars. But it also brings another unwelcome change for Mac OS X users. Google Software update daemon is installed when the application is launched for the first time. The user is greeted with an uninformative message that does not really explain what is about to happen. After the user accepts, Google Update Agent is downloaded and installed. It updates all Google applications and not just Google Earth. Also, it runs on an unchangeable schedule of its own (instead of, say, only when one of Google's apps is launched), consuming system resources. Worst of all it can not be simply removed, since it is downloaded and installed again once Google Earth is launched. Users really have only two choices: live with it, or uninstall all Google apps. There's a discussion about the updater in this Google Group, including details of a way to disable it (not for the faint of heart). So fellow Slashdotters, has Google crossed the line?"
Does anyone have an "in" with somebody at Google Earth or the outfit they contract with to provide the imagery? A large portion of central and northern Arizona hasn't been updated in years i.e. the images are still in low resolution. The reason I ask is that I belong to a Search & Rescue team and we are currently looking for evidence of a downed aircraft reported missing two years ago. However, much of the possible crash area is still way out of date. In general, not having current imagery makes our job more difficult than it should be.
Exactly so. I also don't want to be disturbed with whatever I'm doing by an updater happily sloshing in data in the background. I love Google Earth, but it's been uninstalled now; I might try killing the updater later with the command line, but can't be bothered right now. Seems to be, the best thing we can do is bombard Google. Send them emails with complaints. They'll get the picture, and I think they'll adjust the code - at least enough to only run when you want it to, or on selected components. Now, this might be part of a bigger plan of theirs (world domination, anyone?), likely to force updates of Chrome and other software, but they usually do listen to public opinion. We just have to make it public, and this /. articls is a good start.
A positive attitude may not solve all your problems, but it will annoy enough people to make it well worth the effort.
I don't know that this rises to the level of "evil." On the other hand, I would call it inconsiderate, self-important, and shoddy workmanship.
They did fix one thing in this version that several people complained about: GE 4.3 for Linux required a certain processor flag (SSE2) that 32 bit AMD processors don't have. Strangely, they did not require it for the Windows version; I was able to use GE 4.3 on this AMD Sempron without a problem under Windows.
Fortunately, GE 5.0 doesn't require that flag under Linux. I'm glad they fixed it, because I wasn't going to upgrade my desktop computer just to run the latest GE. GE 4.3 Linux requirements update.
So it appears the team does listen to feedback. I hope they'll listen to this new concern as well.
For goodness sake. Am I the only one that likes the Google Updater?
Let's review the benefits it has:
I think people overestimate the resource drain this app has. Really, this should be a core part of Windows. I'd much rather desktop apps behave like web apps and just get silently better instead of expecting me to give a rats ass about the existence of a 0.0.1 point release.
Looks like it
No, it bloody isn't. That's the sort of thing malware does. My computer is mine and things on it get installed and updated only under my consent.
It's the principle of the thing. This action alone ensured nothing else of Google's will get on my computer.