Not sure about this Keystone, but the Chrome Software Reporter Tool keeps annoying me A LOT. It frequently causes high CPU load and at least the last time I checked I could not find a proper documentation on what it is or does.
Chrome Is Bad
31–40 of 306 posts
Re: Chrome Is Bad
#32It sucks because Chrome is so much better usability wise than all those others. I wish they would just fix whatever this keystone trash is, and leave that to stonehenge
What does Chrome do better than Safari?
Re: Chrome Is Bad
#33Just use Firefox If you want to be sure your stuff works across browsers, test in safari Don’t support or trust ad companies to deliver technology, their interests are always misaligned with the user
A generation ago people used to say "as long as it works in IE6 then that's all you need, who cares about other browsers"
Now it's Chrome, but it's the same danger.
Re: Chrome Is Bad
#34Earlier quoted context omitted.
Safari is arguably the worst browser to do general tests in if you're not making iOS apps, as it has a history of rendering and behaving differently than any other browser. The dev tools are also unusable compared to Chrome.
I think you misunderstood the GP's comment. They aren't advocating to work with Safari, but to work with Firefox then to test with Safari. If it works in Safari after being developed in Firefox, it's likely to work everywhere.
FWIW I haven't found that to be the case with something as simple as making an image autoresize.
Re: Chrome Is Bad
#35Is there anything like this going on on Linux? I don't really use it, but I have it in case I need to do dev testing.
Fortunatelly on Linux it's just using standard repositories.
Re: Chrome Is Bad
#36Keystone is the hidden nefarious program that apple installs as its been clearly stated to convert intel into arm code lol
Re: Chrome Is Bad
#37Looks like this is just a Windows/OS 10 trojan. These sort of bullshit software issues usually come the the territory.
[deleted]
Re: Chrome Is Bad
#38Chrome's security is, however, light years ahead of anyone else's; it remains the sole reason I still use it. It's possible to use Little Snitch to deny Keystone/ksupdate all network access, which is what I do, which removes the Google RCE vulnerability it places on your machine. Make sure to periodically manually update Chrome, however.
I think chrome was the most secure in 2015, but a lot of updates in all browsers have shipped since then!
Also, if you include google in your threat model, then chrome was never that safe
Re: Chrome Is Bad
#39The author went so far as to create a domain for this rant, and yet didn't even do any performance metrics or basic forensic analysis at all. I'm not saying the author is wrong, but there's a lot of questions here. How does Keystone hide itself from the Activity Monitor? Is there a Keystone process if you run `ps aux`? Did you run dtruss/strace? What is it doing when Chrome isn't running that causes it to degrade per…
I'm quite impressed by that “chromeisbad” as a domain was not already taken.
Re: Chrome Is Bad
#40The author went so far as to create a domain for this rant, and yet didn't even do any performance metrics or basic forensic analysis at all. I'm not saying the author is wrong, but there's a lot of questions here. How does Keystone hide itself from the Activity Monitor? Is there a Keystone process if you run `ps aux`? Did you run dtruss/strace? What is it doing when Chrome isn't running that causes it to degrade per…
Possible correlation and hand waving equals causation.
I, too, was hoping for something, well, technical. Considering #1 on hacker news...