8 minutes to compress 1 image? WTF man, that's ridiculous. You get light from the sun in that time.
4:56 am — Tuesday, 21 March 2017
I suspect a similar thing could be done with gzip compression dictionaries - running through the file to be compressed a very large number of times (beyond gzip -9) to select the best dictionary before a final best-compression encoding.

Burn CPU to save disk space and transmission time on stuff to be delivered a lot.

I wonder also if this jpeg compression approach can be factored into MPEG delta compression for movies... again, burn CPU upfront for a better, smaller delivery.
4:59 am — Tuesday, 21 March 2017
Dumb Grub:
This is a bad day for Grubes. Breakthrough tech from Google - and open source! - and gorgeous new phones from Samsung.

And what news from Apple? Oh, different iPads?

9:50 am — Tuesday, 21 March 2017
on compression:
the problem with gzip is that it's stream-based and single-pass with a limited window, so that it can fit into the unix piping streaming thing. reworking it to go through multiple times would be a lot of effort.
11:11 am — Tuesday, 21 March 2017

what's wrong with binhex?
12:49 pm — Tuesday, 21 March 2017
@Dumb Grub

It really is unusably slow, though.

I built it the other day (which was a PITA because they use a screwy build system) and waited 20 minutes for it to process a single image from my SLR.
1:55 pm — Tuesday, 21 March 2017
OK, just pulled the latest tree from github and they fixed the build system, at least.

Still runs slower than natural evolution, though.
2:32 pm — Tuesday, 21 March 2017
Wake up Grubs! There are new iPads to jerk off upon!

Also here's Siri doing something stupid: http://deadspin.com/siri-unaware-women-play-four-quarters-of-basketball-c-1793468986
2:55 pm — Tuesday, 21 March 2017
Cheese Head:
It's a good tradeoff for people that are serving media. A 10% space savings becomes a huge bandwidth saver.

Still, it'll make updating graphics on a website an exercise in patience, something most web people don't have a lot of.

"Photoshop is still saving the image! WTF!"
4:17 pm — Tuesday, 21 March 2017
It’s not going to be a tradeoff that suits everyone: 10% bandwith savings vs 10x (being generous, it’s more like 400x) increase in encoding time means real-time transcoding is impossible, for example.
5:12 pm — Tuesday, 21 March 2017
Mac Pro is Dead:
Lets see how long he waits to post about the new Apple "releases".
6:04 pm — Tuesday, 21 March 2017
Cheese Head:
Is the encoding SSE-aware? Or is that speed already SSE-aware? That'd be brutal.

It's almost like you need a web crawler that goes around in its spare time and compresses images for you.
9:16 pm — Tuesday, 21 March 2017
anonymous anonymous:
Dammit Biff! Even Gruber understands that this is not suitable for real-time work. Guess what? You don't have to sit there and wait for it to finish! Go visit pornhub while you're waiting!
2:41 am — Wednesday, 22 March 2017
> Even Gruber understands that this is not suitable for real work.

1:41 pm — Wednesday, 22 March 2017
Leave a Comment
To leave a comment, install the Safari extension!