background-image: image("wavy.svg", 'wavy.png' , "wavy.gif"); and so on...
It seems that Google lowered emphasis on the project, or is still working on it behind-the-scenes. I'd much prefer to have 'less of images' moving over the web (without cutting back on visuals, you know) and save precious bandwidth.
[1] http://dev.w3.org/csswg/css3-images/#image-fallbacks
And then the fact that Google Chrome has over 30% market share. Makes sense to promote WebP.
http://pngquant.org http://tinypng.org
And while it's not as good as WebP, it's 20% of the filesize you get from Photoshop.
Larger photo-based images will always look terrible, no matter which kind of dithering is used.
I've got a pretty large collection of PNGs to test quantisation on and 68% of them end up converted in great quality, 89% are within acceptable range. It's about double of what you can get with Fireworks.
And for images that can't absolutely fit in 256-colors there's a hack for lossy true-color PNGs that can reduce size by 20-40%: https://github.com/pornel/mediancut-posterizer
If quantized PNG8s aren't good enough, you can only use gigantic PNG32 files, which are over 5 times larger than JNG or WebP files. I've seen websites which were over 5MB thanks to that limitation. It's ridiculous.
I wish they had at least kept JNG. It's a fairly simple JPG/PNG mashup format. If you already use JPG and PNG libraries, supporting JNG won't add much weight.