He dove in to the cruft, initially on Gmail Chat, but over time more and more on core Gmail. He began agitating for change, which culminated in this new design.
Aaron continues to tell that at Google, people test-drive all their own products, e.g. using Gmail all day long (is Marissa Mayer an exception? She once told Fortune/ CNN, “I use Gmail for my personal e-mail – 15 to 20 e-mails a day – but on my work e-mail I get as many as 700 to 800 a day, so I need something really fast,” referring to email client Pine). Aaron says that a lag of half a second, for instance, is usually considered great for web applications, but that such amounts are still considered long for Gmail by some of those working on it. Aaron writes:
Because of this, the Gmail team has been to hell and back several times over the course of this project, trying to shave milliseconds off frequent operations.
As one small example, one team member reverse-engineered jscript.dll to figure out how its GC [garbage collection] algorithm worked, and was horrified to find that it had hard-coded, arbitrary limits on how many objects could be allocated before a GC would occur. This led to an insane amount of effort optimizing the code to reduce the number of allocations in core code paths.
>> More posts