Leaflet@lemmy.world to Firefox@lemmy.mlEnglish · 2 months agoFirefox will consider a Rust implementation of JPEG-XL (with Google's help)github.comexternal-linkmessage-square10fedilinkarrow-up1187arrow-down12cross-posted to: linux@lemmy.mljpegxl@lemmy.world
arrow-up1185arrow-down1external-linkFirefox will consider a Rust implementation of JPEG-XL (with Google's help)github.comLeaflet@lemmy.world to Firefox@lemmy.mlEnglish · 2 months agomessage-square10fedilinkcross-posted to: linux@lemmy.mljpegxl@lemmy.world
minus-square1984@lemmy.todaylinkfedilinkarrow-up11arrow-down2·2 months agoIt’s sad to see how Mozilla needs Google even for this. I hate that Google seems to have a finger in absolutely everything. Why? Because their end goal is a web where you need to identity yourself to them.
minus-squarepivot_root@lemmy.worldlinkfedilinkarrow-up22arrow-down1·2 months agoGoogle created the original reference implementation, libjxl. It’s not stupid that they would prefer a Rust rewrite be created by the same team. https://github.com/libjxl/libjxl
minus-squaredan@upvote.aulinkfedilinkarrow-up16·edit-22 months agoIt’s likely that Google offered, and Mozilla doesn’t have a reason to say no. Google Research do this for a bunch of open source projects. Chrome needs a JPEG-XL decoder too, so I’d guess they’re going to share the code across both Chrome and Firefox.
It’s sad to see how Mozilla needs Google even for this.
I hate that Google seems to have a finger in absolutely everything. Why? Because their end goal is a web where you need to identity yourself to them.
Google created the original reference implementation, libjxl. It’s not stupid that they would prefer a Rust rewrite be created by the same team.
https://github.com/libjxl/libjxl
It’s likely that Google offered, and Mozilla doesn’t have a reason to say no. Google Research do this for a bunch of open source projects.
Chrome needs a JPEG-XL decoder too, so I’d guess they’re going to share the code across both Chrome and Firefox.
deleted by creator