Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Why BPG will replace GIFs and more. Parent comment
Encoding those 369 PNG files to a LOSSLESS BPG animation (using bpgenc 0.9.6 with options -lossless -a) produces a .bpg file of about 50MB.
Encoding them to APNG (using apngasm 2.7) results in a 57MB animated PNG file.
The corresponding progressive FLIF animation is 20 MB.
Obviously it is not a good idea to losslessly encode lossy images/movies, as a lot of bytes are wasted on encoding compression artifacts.
There are no comments on this comment yet.
Encoding those 369 PNG files to a LOSSLESS BPG animation (using bpgenc 0.9.6 with options -lossless -a) produces a .bpg file of about 50MB.
Encoding them to APNG (using apngasm 2.7) results in a 57MB animated PNG file.
The corresponding progressive FLIF animation is 20 MB.
Obviously it is not a good idea to losslessly encode lossy images/movies, as a lot of bytes are wasted on encoding compression artifacts.