5 ms·

I rather them to slow down and address the performance issues.

by hartator 6y ago

lukifer 6y ago
Have they given any follow-up to the https://chromeisbad.com https://chromeisbad.com fiasco?
- jasonvorhe 6y ago
  Has there ever been a deeper investigation into this that goes beyond "I did a thing on my computer and something changed somehow"?
- coldtea 6y ago
  Well, if by "fiasco" we mean "a random person wrote some random observations about his computer and chrome on some random website" then, probably they don't really need to follow up on it...
  - vinger 6y ago
    I think it's important and may explain a lot. The fact that they started looking into this is a good sign. I've always wondered what the slowdown with having chrome or not was and this could explain it.
  - lukifer 6y ago
    Loren Brichter is a long-time Mac developer and hardly a "random person"; and his claims were based on anecdata from multiple machines and Twitter reports. Pareidolia is certainly a reasonable null-hypothesis (similar to 99% of computing rain-dances, like repeated defragmentation, or "closing" iOS apps). But assuming the problem isn't completely coincidental or imagined, it would still be good to get to the bottom of it, whether the root problem is Apple's or Google's. Just now noticed the bug-tracker thread: https://bugs.chromium.org/p/chromium/issues/detail?id=1158402#c18 https://bugs.chromium.org/p/chromium/issues/detail?id=115840...
- smoldesu 6y ago
  Looks like a MacOS issue to me. I used Chrome for years on my x201 with i3, it idled only a few degrees above room temp with Chrome open.
war1025 6y ago
Release cadence and performance issues are orthogonal. Frequent releases just mean you get updates as they become available. That doesn't mean they can't take on longer-term issues that need several release cycles to complete.
jeffbee 6y ago
Chrome project has a pretty robust system of continuous benchmarking where regressions are automatically detected and filed as bugs, and the causing CLs are automatically found by bisection. For example, a recent regression: https://bugs.chromium.org/p/chromium/issues/detail?id=1176565 https://bugs.chromium.org/p/chromium/issues/detail?id=117656... What, in your expert opinion, is missing from this regime?

I rather them to slow down and address the performance issues.

lukifer 6y ago

Have they given any follow-up to the https://chromeisbad.com https://chromeisbad.com fiasco?

jasonvorhe 6y ago
Has there ever been a deeper investigation into this that goes beyond "I did a thing on my computer and something changed somehow"?
coldtea 6y ago
Well, if by "fiasco" we mean "a random person wrote some random observations about his computer and chrome on some random website" then, probably they don't really need to follow up on it...
- vinger 6y ago
  I think it's important and may explain a lot. The fact that they started looking into this is a good sign. I've always wondered what the slowdown with having chrome or not was and this could explain it.
- lukifer 6y ago
  Loren Brichter is a long-time Mac developer and hardly a "random person"; and his claims were based on anecdata from multiple machines and Twitter reports. Pareidolia is certainly a reasonable null-hypothesis (similar to 99% of computing rain-dances, like repeated defragmentation, or "closing" iOS apps). But assuming the problem isn't completely coincidental or imagined, it would still be good to get to the bottom of it, whether the root problem is Apple's or Google's. Just now noticed the bug-tracker thread: https://bugs.chromium.org/p/chromium/issues/detail?id=1158402#c18 https://bugs.chromium.org/p/chromium/issues/detail?id=115840...
smoldesu 6y ago
Looks like a MacOS issue to me. I used Chrome for years on my x201 with i3, it idled only a few degrees above room temp with Chrome open.

war1025 6y ago

Release cadence and performance issues are orthogonal. Frequent releases just mean you get updates as they become available. That doesn't mean they can't take on longer-term issues that need several release cycles to complete.

jeffbee 6y ago

Chrome project has a pretty robust system of continuous benchmarking where regressions are automatically detected and filed as bugs, and the causing CLs are automatically found by bisection. For example, a recent regression: https://bugs.chromium.org/p/chromium/issues/detail?id=1176565 https://bugs.chromium.org/p/chromium/issues/detail?id=117656... What, in your expert opinion, is missing from this regime?