But, sometimes Google engineers have huge blind spots. Often they are just general purpose smart engineering students. I've met plenty who couldn't deal with piping on the command line. It's barely plausible that nobody on the team even knew there were GIFs with smaller look-up tables, or the overhead involved in dithering or making smoother transitions.
Come to think of it, I bet this is what really happened: they were reusing map tiles from Maps and didn't even consider making their own. So, maybe this guy built a whole new tile generation pipeline for mobile, or figured out some way to remap colors from existing tiles into a smaller look-up table without sacrificing too much quality. That could be legitimately heroic.
But yeah that quote isn't the best.
Of course to design an algorithm to find a good smaller color depth that closes to original color depth is not an easy engineering issue. I guess it is this part that the reporter messed up the story and made it sounds so ridiculous to techies.
http://en.wikipedia.org/wiki/Color_quantization
I don't know what you mean by adapting it to Google's infrastructure. I think you meant to say "shared nothing". Tile serving is perfectly suited to such an architecture already. There's no shared state across tiles, for instance.
in http://en.wikipedia.org/wiki/Graphics_Interchange_Format it mentions:
"The algorithms used to select the palette and to perform the dithering vary widely in output quality. Additionally, dithering significantly reduces the image's compressibility and thus works contrary to GIF's main purpose."
So to goal is to get the best color palette that satisfies
1. The resulting image quality is close to original image,
2. The compressed image has to be smaller than original
3. The color quantization can be automated without too much human supervision.
I think the general color quantization algorithms may solve the point 1 and 3 but not necessary point 2.
Never mind, I am an idiot sometime.