48 ms·
I wonder how much the in-house expertise of developing Chrome is contributing to the GoogleBot analysis stuff. Having people who aren't afraid to go knee deep
by shabble 15y ago
I wonder how much the in-house expertise of developing Chrome is contributing to the GoogleBot analysis stuff. Having people who aren't afraid to go knee deep in WebKit and produce some nice fast library for partially evaluating layouts, etc, is probably quite a nice thing.
As one of the sibling comments here mentions, ad detection is a pretty well-solved problem by now, through size, position and origin matches. The interesting part here I think is how they're actually doing the 'virtual rendering' (and presumably, reflowing it for each of their mentioned typical browser resolutions) to check what's actually 'above the fold'.
- joshu 15y agoi suspect that the cpu time to even partially render a page via webkit is really expensive at scale. that said, i recall there was a headless chrome that someone built - anyone remember where that is?
- joshu 15y agoanswered my own question: http://www.phantomjs.org/ http://www.phantomjs.org/
- Chirono 15y ago| I wonder how much the in-house expertise of developing Chrome is contributing to the GoogleBot analysis stuff If anything, I expect the contribution worked the other way, with the rendering engine being developed purely for search, and then fleshed out into a full browser. There was an interesting post about this a few months ago: http://news.ycombinator.com/item?id=3182579