netnichols
Joined 16 years ago
Karma
321
Submissions
87
Member since
Jun 16
Joined 16 years ago
My first guess would be that they snapshot the DOM in the JS tick immediately after window.onload completes. Maybe they have a short pause to let any fast timeouts or callbacks complete, but there's got to be a cutoff at some point (e.g. to stop an infinite wait for pages that continuously update a relative date). Of course, with their own JS engine, I bet they can get really fancy with the heuristics to determine when to take that snapshot.
A hugely popular (for its market), established, independent, and profitable software company gives clear and transparent insight into how the past year has gone for them and their products.
But the walls are indeed very thick!
It might not actually be my first choice, but this one of the few on my short list that no one else has mentioned.
I read it in my mid teens (not too long after we stopped playing Rambo in the back yard) and it profoundly affected the way I view war, violence, and suffering. I've only read it the once (almost 25 years ago), and I hardly remember the story at all, but I vividly remember the feeling that it gave me.