Firefox

20357 readers

66 users here now

/c/firefox

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

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 5 years ago

MODERATORS

k_o_t@lemmy.ml

golden_zealot@lemmy.ml

186

Firefox will consider a Rust implementation of JPEG-XL (with Google's help) (github.com)

submitted 10 months ago by that_leaflet@lemmy.world to c/firefox@lemmy.ml

10 comments fedilink hide all child comments

all 11 comments

sorted by: hot top controversial new old

[–] vzq@lemmy.blahaj.zone 50 points 10 months ago

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.

[–] lnxtx 14 points 10 months ago

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

[–] pivot_root@lemmy.world 11 points 10 months ago (1 children)

Interestingly, the reference implementation libjxl appears to be a Google project. They're all over the patents file and CLA.

If Mozilla isn't merely being hopeful about having the same team create a Rust implementation, that might actually mean there's internal interest within Google. Assuming they pull it off, the bullshit reason for refusing to add JPEG XL to Chromium might finally stop being a blocker.

[–] morrowind@lemmy.ml 6 points 10 months ago (1 children)

Google basically made jxl. I'm sure there's plenty of interested people in there, it's always just been the chromium team blocking it

[–] pivot_root@lemmy.world 4 points 10 months ago* (last edited 10 months ago)

It's not the Chromium team. Google could have added JPEG XL to Android, but that's been stalled for nearly two years with zero explanation as for why.

The whole thing smells of managerial interference somewhere.

[–] missphant@lemmy.blahaj.zone 11 points 10 months ago

The dream lives on.

[–] 1984@lemmy.today 10 points 10 months ago (3 children)

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.

[–] pivot_root@lemmy.world 21 points 10 months ago

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

[–] dan@upvote.au 16 points 10 months ago* (last edited 10 months ago)

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.

[–] independantiste@sh.itjust.works 10 points 10 months ago

♥️ jpegxl