I'm really disappointed to see that article posted on tom's guide! Loren Brichter's website isn't particularly well written. His claims are anecdotal and he provides no evidence or even detail about them. His recommendations are subjective, so I wouldn't take his advice.
I don't know much about Keystone, except that it's open source, which means anyone can peak inside. This tends to mean that anything bad could and would have been spotted and fixed, in my opinion.
I'm not saying that Chrome hasn't or doesn't cause performance issues in certain scenarios/environments, but I do think that it isn't likely to be that many people (as in all software). In fairness Birchter's appears to be an edge case
Various counts put Chrome global market share at ~65%-71% of ~3.734bn-4.66bn unique users. Birchter claims that Keystone has been a thorn in the side of mac users since 2009. I would argue that the stats suggest he is in the minority.
I use chrome and have it configured to run apps in the background too so it can be quite resource hungry at times, however it's never been the source of any performance issues. Now it's my word against his.
Anyway tom's guide's almost blind replication of Birchter's article without any commentary or independent testing or verification of his claims has killed my opinion of it. I probably not rely on advice from here again.
Facebook
Twitter