News for hackers. Stuff that matters.
Re:Hey Ho, GIFs Must Go (1999) by grenoire on Saturday October 26, 2019 @11:58AM (#21364422)
WebP is lossy though, no? The whole point of PNG is preserving the exact pixel data.
Re:Hey Ho, GIFs Must Go (1999) by javagram on Saturday October 26, 2019 @12:04PM (#21364458)
APNG is finally supported in every browser but IE/old Edge, so that case will be fixed soon too.

There’s also a lossless webp variant.

Re:Hey Ho, GIFs Must Go (1999) by daef on Saturday October 26, 2019 @01:04PM (#21364824)
https://flif.info beats lossless webm
Re:Hey Ho, GIFs Must Go (1999) by mceachen on Sunday October 27, 2019 @06:21AM (#21368845)
Re:Hey Ho, GIFs Must Go (1999) by chungy on Saturday October 26, 2019 @02:46PM (#21365455)
WebP has lossy and lossless modes. The latter should be considered as the PNG replacement :)
Re:Hey Ho, GIFs Must Go (1999) by lazyjeff on Saturday October 26, 2019 @04:48PM (#21366076)
WebP should be replacing JPEG and PNG. I feel like JPEG/PNG is like the GIF of 1999, formats which can be completely replaced with no real drawbacks. The disk space and network savings alone could reduce energy consumption. Safari is the only browser without WebP support, and I don't think it makes sense to keep waiting on them. If Safari users start seeing websites with images that don't load, Apple will support WebP real quick.

One thing that would be nice would be a way to tell whether a WebP is lossy (in which case you should only edit/resize the original file, to prevent degradation), or lossless (edit as much as you please).

Re:Hey Ho, GIFs Must Go (1999) by xvilka on Saturday October 26, 2019 @10:52PM (#21367619)
Apple users can also help by complaining[1] more. Interestingly, there is a bug[2] in Microsoft Edge which wasn't touched for months as well.

[1] https://discussions.apple.com/thread/250073758

[2] https://developer.microsoft.com/en-us/microsoft-edge/platfor...

Re:Hey Ho, GIFs Must Go (1999) by biddlesby on Saturday October 26, 2019 @05:19PM (#21366287)
It's wishful thinking that it would reduce energy consumption! If the format is more efficient people will just load more.
Re:Hey Ho, GIFs Must Go (1999) by TheSpiceIsLife on Saturday October 26, 2019 @07:46PM (#21367041)
Jevons Paradox:

In economics, the Jevons paradox (/ˈdʒɛvənz/; sometimes Jevons effect) occurs when technological progress or government policy increases the efficiency with which a resource is used (reducing the amount necessary for any one use), but the rate of consumption of that resource rises due to increasing demand.

https://en.wikipedia.org/wiki/Jevons_paradox

Re:Hey Ho, GIFs Must Go (1999) by zzo38computer on Saturday October 26, 2019 @02:47PM (#21365459)
I think FLIF seems better as a PNG replacement. FLIF is a lossless format, although lossy encoding is also available. Still, PNG is much better than GIF, so GIF should not be used unless you need it for use with software that can't use PNG.

(This kind of lossy encoding would be possible with PNG too, but most PNG encoders don't have a lossy mode.)

(GIF is now patent-free, but PNG and FLIF are still better compression than GIF anyways.)

Re:Hey Ho, GIFs Must Go (1999) by ZeroGravitas on Saturday October 26, 2019 @02:59PM (#21365520)
The FLIF author's next project FUIF is now partly the basis for JPEG XL which replaces (or at least aims to replace) PNG and all the other standard web formats.

Pngs get used for both for non photographic images and photographic images with alpha channel, and JPEG XL should win on both of those use cases.

It also cleverly has an upgrade story forexisting JPEGs so I imagine a fairly quick uptake where a proxy can recompress an existing sites images and get better size with no recompression loss.

Re:Hey Ho, GIFs Must Go (1999) by chungy on Saturday October 26, 2019 @03:26PM (#21365655)
I like FLIF too, but it has zero browser support, whereas all Chromium and Gecko browsers support WebP.

Something nice about FLIF is partial decoding. You can reasonably see a thumbnail by downloading just 5% of the full lossless file.

Re:Hey Ho, GIFs Must Go (1999) by ZeroGravitas on Sunday October 27, 2019 @07:32AM (#21369102)
This feature has been carried through to his work on JPEG XL, which is co-created with Google (using their Pik and Brunsli tech) and so fairly likely to get wide browser support.

In conjunction with HTTP2 to progressively load all visible images first, this is a killer feature for the web, simplifying thumbnails and responsive design while vastly speeding up page loads and improving caching.

Re:Hey Ho, GIFs Must Go (1999) by Lorin on Sunday October 27, 2019 @01:20AM (#21368004)
FLIF needs a catchier, pronounceable file extension name.
Re:Hey Ho, GIFs Must Go (1999) by ahbyb on Saturday October 26, 2019 @03:05PM (#21365534)
Is it supported at all by safari?
Re:Hey Ho, GIFs Must Go (1999) by gsich on Saturday October 26, 2019 @07:57PM (#21367076)
As Safaris usage is very low: likely not an issue.
Re:Hey Ho, GIFs Must Go (1999) by ckorhonen on Saturday October 26, 2019 @09:51PM (#21367431)
If you factor in iOS, usage is actually quite significant. Almost a accounting for almost a third of the market, making it the second most popular browser.

https://www.stetic.com/market-share/browser/

Re:Hey Ho, GIFs Must Go (1999) by gsich on Saturday October 26, 2019 @11:17PM (#21367698)
I don't.
Re:Hey Ho, GIFs Must Go (1999) by coribuci on Saturday October 26, 2019 @06:03PM (#21366529)
Right. Every day a new format.
Re:Hey Ho, GIFs Must Go (1999) by nebulous1 on Saturday October 26, 2019 @12:23PM (#21364569)
webp has both lossy and lossless compression