Release note:
https://groups.google.com/a/webmproject.org/group/webp-discu...
The code is actually rather interesting to read -- it basically uses K-means for a large portion of the encoding process, which is applicable in this case because of VP8's non-adaptive arithmetic coder. I've never seen an encoder done quite this way before.
I cannot find any comparison, but that's because WEBP is a very bad name for searching on google: it gets shortened to 'web'.
http://code.google.com/speed/webp/
Which elsewhere claims that 99 human years are wasted due to uncompressed web content each day.
http://code.google.com/speed/articles/use-compression.html
Opera certainly seem to think they can compress and decompress the WebP image on-the-fly and still come out ahead speed-wise compared with the original (at a cost of quality) and their old JPEG system (with improved quality), at least over low-bandwith connections.
My great-grandfather's surname is Aland. I did some searching on him recently - a search for "Aland" also returns results for "Al and" and "a land", neither of which are relevant. Using the + prevents that.
Theoretically better compression than JPEG (but ... so was JPEG-2000).
Disadvantages:
The encoder actually loses to JPEG in many tests and almost everything it encodes looks like a blurry mess.
No support for any color format besides 4:2:0.
Almost no support in image editing applications.
An order of magnitude slower than JPEG.
Somehow I don't think this is much of a "JPEG killer". Its technology is 10 years out of date, entirely copy-pasted from H.264, and its featureset isn't even close to equalling JPEG's, let alone adding new features that people wanted.