RustyChainsawEnema@lemmy.dbzer0.com to Comic Strips@lemmy.world · 1 day ago[xkcd 1683] Digital Datalemmy.dbzer0.comimagemessage-square29fedilinkarrow-up1397arrow-down14file-textcross-posted to: 196@lemmy.blahaj.zoneitsme@lemm.ee
arrow-up1393arrow-down1image[xkcd 1683] Digital Datalemmy.dbzer0.comRustyChainsawEnema@lemmy.dbzer0.com to Comic Strips@lemmy.world · 1 day agomessage-square29fedilinkfile-textcross-posted to: 196@lemmy.blahaj.zoneitsme@lemm.ee
minus-squareTheBrideWoreCrimson@sopuli.xyzlinkfedilinkarrow-up2·1 day agoSee, that’s why I started using JPEG-XL for long-term storage. Apart from being better in every aspect for lossless and near-lossless still images than any competitor, the generation loss even over 1000 lossy save and load cycles is negligible.
minus-squarestevedice@sh.itjust.workslinkfedilinkEnglisharrow-up1·21 hours agoThat really doesn’t matter when someone screenshots your JPEG-XL and posts it in a website that transcodes it to WEBP and adds a water mark.
![[xkcd 1683] Digital Data](https://lemmy.dbzer0.com/pictrs/image/6b5b434e-7bdc-4025-b04d-21e700d25079.webp){kind=link}
See, that’s why I started using JPEG-XL for long-term storage. Apart from being better in every aspect for lossless and near-lossless still images than any competitor, the generation loss even over 1000 lossy save and load cycles is negligible.
That really doesn’t matter when someone screenshots your JPEG-XL and posts it in a website that transcodes it to WEBP and adds a water mark.