A new (slow) open source JPEG algorithm makes images 35% smaller and looks better than older compression systems

[OtherMichael]

@Boundegar

Now imagine if Microsoft owned it.

It can also do mail merge, arrays are indexed from 1, and it tries to upsell you to OneDrive.

[redesigned]

@Boundegar

So it’s extremely slow now. What are the chances it won’t be improved inside of a year?

it is slow because it uses more compression optimization passes and a larger data look back window. they are planning on adding some GPU optimizations, but it isn’t ever going to be a real-time compressor, rather a pre-processing compressor. You wouldn’t have apache run this on the fly, but you might pre-compress all your images prior to uploading them, especially the critical ones.

@doctorow

The authors don’t quantify “extremely” slow, but note that it “may be too slow for many practical uses.”

~ 1 minute / MPixel on a 2.6 GHz Xeon

[Kimmo]

@LockeCJ

I’m going to use this as an excuse to link to BPG.

Holy crap! That’s the bee’s knees!

But given the total lack of traction APNG has garnered (granted, that’s only a fraction as awesome as this), has the situation been locked in since the 90s?

Maybe we all need to just be like, BPG! BPG! BPG! all of the time…

[LockeCJ]

BPG seems like a better solution given that the decoder can be included in the web page, so the browser doesn’t have to support it natively.

[redesigned]

Cool BPG uses HEVC 256. I’ve been impressed with HEVC 256. It works significantly better on originals, compared to recompressing, and on higher resolution over lower.