earlier replies
Replying to @WithinRafael @taviso
Having worked on browser engines, I don't think this is a straightforward example of poor code. There are many optimizations that the complexity of the web platform means you have to disable in more complex conditions. (1/?)
1
7
For example, if you're using some specialized video or graphics pipeline isn't designed to deal with other things on top of it (common), you'd need to test for the case of "things on top of it" and avoid using the optimization in that case. (2/?)
1
2
Then it just comes down to how sophisticated the test for overlapping content is. In this case, it sounds like it wasn't very sophisticated -- but it was probably still good enough to be an effective optimization on lots of sites. Worth improving, definitely. (3/?)
1
2
Replying to @davidbaron @WithinRafael @taviso
But I don't think failing to make a particular premature optimization (i.e., optimization without yet seeing the need for it) implies that somebody's code is bad. Graphics on the web has tons of performance cliffs; lots of folks teach these days about how to avoid Chrome's. 4/4

Dec 19, 2018 · 10:32 PM UTC

1
3