4 ms·

Browsers don't support it out of the box (yet), so probably not time to switch. Try AVIF instead. It has similar efficiency and feature set and is better suppor

Browsers don't support it out of the box (yet), so probably not time to switch. Try AVIF instead. It has similar efficiency and feature set and is better supported. https://caniuse.com/jpegxl https://caniuse.com/jpegxl https://caniuse.com/avif https://caniuse.com/avif

brycewray 4y ago
AVIF will be a good choice in time, but right now it takes a lot of horsepower (read: battery juice) for some devices to use it. Not sure how/when that'll get resolved. From “The ROI of Adopting AVIF for Websites” on the Cloudinary Blog, 2021-11-29[0]: > . . . since AVIF decoding consumes a lot of CPU and battery, mobile devices are taking a while to jump on the AVIF bandwagon. [0]: https://cloudinary.com/blog/the_roi_of_adopting_avif_for_websites https://cloudinary.com/blog/the_roi_of_adopting_avif_for_web...
dontbenebby 4y ago
>Browsers don't support it out of the box (yet), so probably not time to switch. Ok, so do we skip even trying to use more well tested stuff like APNG to use this? Or just accept the moment is as gone as the blink tag? (I'm only being half joking -- I'm not a data visualization expert but I learned digital photography when you'd shoot onto a floppy jammed into the camera, so while I don't know algos well, I've also seen scores of security vulnerabilities stem from browser cruft. Classic example being that prior to FTP support being removed from firefox, you could do things like say go to trusteddomain.nameofschool.edu@badsitethatistotallyfullofputinsmalware.ru and very easily infect any sort of kiosk running Firefox, Firebird, or in one especially hilarious case... Internet Explorer. I'm not even joking... my target was still using Internet Explorer, on a kiosk, years after the switch to Edge. (Luckily all I did was redirect to a search engine to find an ISBN number. I could have done much worse.)

brycewray 4y ago

AVIF will be a good choice in time, but right now it takes a lot of horsepower (read: battery juice) for some devices to use it. Not sure how/when that'll get resolved. From “The ROI of Adopting AVIF for Websites” on the Cloudinary Blog, 2021-11-29[0]: > . . . since AVIF decoding consumes a lot of CPU and battery, mobile devices are taking a while to jump on the AVIF bandwagon. [0]: https://cloudinary.com/blog/the_roi_of_adopting_avif_for_websites https://cloudinary.com/blog/the_roi_of_adopting_avif_for_web...

dontbenebby 4y ago

>Browsers don't support it out of the box (yet), so probably not time to switch. Ok, so do we skip even trying to use more well tested stuff like APNG to use this? Or just accept the moment is as gone as the blink tag? (I'm only being half joking -- I'm not a data visualization expert but I learned digital photography when you'd shoot onto a floppy jammed into the camera, so while I don't know algos well, I've also seen scores of security vulnerabilities stem from browser cruft. Classic example being that prior to FTP support being removed from firefox, you could do things like say go to trusteddomain.nameofschool.edu@badsitethatistotallyfullofputinsmalware.ru and very easily infect any sort of kiosk running Firefox, Firebird, or in one especially hilarious case... Internet Explorer. I'm not even joking... my target was still using Internet Explorer, on a kiosk, years after the switch to Edge. (Luckily all I did was redirect to a search engine to find an ISBN number. I could have done much worse.)