Claims to want more feedback. "Blog" post has no comment field.
Button: http://prntscr.com/kyrhrf
Email Opened: http://prntscr.com/kyri1i
61–70 of 475 posts
Claims to want more feedback. "Blog" post has no comment field.
Button: http://prntscr.com/kyrhrf
Email Opened: http://prntscr.com/kyri1i
Hopefully there was also an update to the privacy policy reflecting the new meaning of being signed into chrome?
Earlier quoted context omitted.
I don't understand, the piece looks like it promises to address all the problems highlighted in the past few days in Chrome 70. Why are you saying it is a PR piece?
Because there's literally nothing they could've said that would make them change their mind. This is the most reasonable response Google could've given. They've addressed every issue as promptly as possible, yet people just dismiss is as PR. It's a lose-lose battle, no matter what they do, people like this will always spin it in a negative way with zero justification.
Surprised to say that not much has changed with the move. I was able to find all my extensions in the firefox addons. Life continues
Earlier quoted context omitted.
I don't understand, the piece looks like it promises to address all the problems highlighted in the past few days in Chrome 70. Why are you saying it is a PR piece?
Because there's literally nothing they could've said that would make them change their mind. This is the most reasonable response Google could've given. They've addressed every issue as promptly as possible, yet people just dismiss is as PR. It's a lose-lose battle, no matter what they do, people like this will always spin it in a negative way with zero justification.
This is PR. It's damage limitation.
Earlier quoted context omitted.
I don't understand, the piece looks like it promises to address all the problems highlighted in the past few days in Chrome 70. Why are you saying it is a PR piece?
The problems were easily foreseeable, and they did it anyway. Anyone who accepts this as "listening the users", and addressing the issues will likely get burned again in the future. Google is a advertising company. Their customers are not their users, and therefore I think things are unlikely to change.
Interesting concept. Care to expound? Would be interested in hearing more.
This is not attempting to fit user needs, this is an attempt to put out a PR fire and salvage quarterly earnings. I'm still leaving, maybe even more-so because of the false heartfelt "ok let's do it your way". I will not be patronized, we're not on the same team anymore.
I don't understand, the piece looks like it promises to address all the problems highlighted in the past few days in Chrome 70. Why are you saying it is a PR piece?
Earlier quoted context omitted.
Neither of those bugs have to do with 100% CPU on rMBP. Their about using an inefficient presentation path which increases GPU power usage. You can mitigate this today by setting gfx.compositor.glcontext.opaque to true. Further, Firefox Beta has additional texture upload performance improvements that will reduce cpu usage. If you're actually experiencing 100% cpu usage, post a profile using https://perf-html.io/ and…
Steps to reproduce: 1) Pick a rMBP. Any one. 2) Set display options - "more space" under System Preferences. 3) Run Firefox. Load any website. No extensions; safe mode doesn't matter. 4) 100%+ CPU, fans kick up and run high, system gets hot and slows to a crawl. Chrome and Safari run totally fine under the same conditions. It's documented pretty thoroughly in the first Bugzilla link I posted; the second one is an off…