Chrome Is Bad

Short story: Google Chrome installs something called Keystone on your computer, which nefariously hides itself from Activity Monitor and makes your whole computer slow even when Chrome isn't running. Activity Monitor showed *nothing* from Google using the CPU, but WindowServer was taking ~80%, which is abnormally high (it should use <10% normally).Doing all the normal things (quitting apps, logging out other users, restarting, zapping PRAM, etc) did nothing, then I remembered I had installed Chrome a while back to test a website.I deleted Chrome, and noticed Keystone while deleting some of Chrome's other preferences and caches. If the Servo team regroups, I'd be inclined to recommend anything they make down the road).Wired first reported on Keystone in 2009, when Google put it into Google Earth. Why would auto-update software need to take up a massive portion of CPU on a ton's of people's computers, all while hiding itself?To all the good people at Google who work on Chrome: something is going on between the code you're writing and what is happening on people's computers.