In a little less than a week, Google's Guetzli JPEG encoder has been able to garner both friends and
foes, or supporters and skeptics.
Here are a few tweets, some including longer form posts surrouding it's release and performance.
@kornelski IMO major caveats with Guetzli. Intentionally exits at qualities below 84 due to artifacting. 20min for one 4k image.— Richard Kuo (@richardykuo) March 16, 2017
@HenriHelvetica For q90+ only, poor on lossy image input, no progressive, ~100x encode CPU, and giant giant memory footprint? No thanks.— Nick Doyle (@njdoyle) March 17, 2017
Guetzli does not encode JPEG progressively, although that is commonly recommended. Interesting. https://t.co/Qo3msLmOE0— Walter Ebert (@walterebert) February 19, 2017
@HenriHelvetica A more sane, 2megapixel image took about 1.5minutes, hit 1GB of mem and DSSIM delta was 0.00011819 (very good)— Jason Ormand (@okor) March 17, 2017
Thought you might like the last tweet for kicks. Nonetheless, you know what they say: opinions are like mobile phones - most people have one. But Guetzli has been open sourced, so all are free to provide input and improvements.