50 points

This decision has probably saved us from a decade long trickle of very embarrassing security vulnerabilities.

And has also gifted us a decade of less, but also more interesting, security vulnerabilities.

permalink
report
reply
14 points

Good algorithm, bad name. JPEG Extra Large.
O.g. JPEG has bad reputation, because of visual artifacts.

permalink
report
reply
11 points

The dream lives on.

permalink
report
reply
10 points

♥️ jpegxl

permalink
report
reply
10 points

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.

permalink
report
reply
21 points

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

permalink
report
parent
reply
16 points
*

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.

permalink
report
parent
reply
2 points
Deleted by creator
permalink
report
parent
reply

Firefox

!firefox@lemmy.ml

Create post

A place to discuss the news and latest developments on the open-source browser Firefox

Community stats

  • 1.9K

    Monthly active users

  • 887

    Posts

  • 17K

    Comments

Community moderators