I hope that we can finally discuss image formats without it getting torpedo'd with "jxl is the format Google doesn't want you to use"
I'm also curious if the decoder being in Rust pays off into tangibly less surface considering how devastating the libwebp and libvpx memory exploits were, I suppose only time will tell
Also consider that libjxl 0.12, which was released in july, contained several security fixes (to the degree that there's a suggestion to upgrade at the top of their README).
I think this validates Google's and Mozilla's decision to hold off until there's a viable Rust alternative (whether that was an explicitly stated reason, as in Mozilla's case, or just happenstance).
Extensive security and hardening fixes across the core decoder/encoder, box
buffers, and plugins (EXR, GIF, APNG/PNG, PAM/PNM/PGX). This includes fixes
for integer overflows/underflows, out-of-bounds reads/writes, buffer
overflows, and null pointer guards
If you’re making an analogy to JPEG being “jay-peg”, wouldn’t JXL’s corresponding pronunciation be something like “jay-ksill” or “jay-zull”? I’m not sure if that’s what you already meant by “xl” – that’s an ambiguous way of describing a sound.
“Jay-eks-ell”, pronouncing each letter, feels most natural to me. Just like I call PNG files “pee-en-jee”. At three syllables, it’s longer than some other proposed options, but I’m not sure if any shorter pronunciation will become widely known.
regalialong | a day ago
\o/
I hope that we can finally discuss image formats without it getting torpedo'd with "jxl is the format Google doesn't want you to use"
I'm also curious if the decoder being in Rust pays off into tangibly less surface considering how devastating the libwebp and libvpx memory exploits were, I suppose only time will tell
mort | 10 hours ago
Also consider that libjxl 0.12, which was released in july, contained several security fixes (to the degree that there's a suggestion to upgrade at the top of their README).
I think this validates Google's and Mozilla's decision to hold off until there's a viable Rust alternative (whether that was an explicitly stated reason, as in Mozilla's case, or just happenstance).
regalialong | 9 hours ago
Oh damn I didn't know about that, for sure then.
freddyb | a day ago
Certainly can't be worse :)
confusomu | a day ago
With Chrome and Firefox finally shipping JPEG-XL, this nerd-rock song pleading for the format changes meaning. We have given JXL a chance!
JulianSildenLanglo | a day ago
Biggest question is should
.jxlbe pronounced "jexl" or "jay-exl"?m_eiman | a day ago
hard g, x, l
in keeping with graphics file extension history :]
noirscape | a day ago
I propose jixel. Like pixel, but with a j. That's what the abbreviation looks like to me.
quasi_qua_quasi | a day ago
This is how I say it.
ag | a day ago
Jay - xl Just like jpeg was jay-peg
roryokane | 17 hours ago
If you’re making an analogy to JPEG being “jay-peg”, wouldn’t JXL’s corresponding pronunciation be something like “jay-ksill” or “jay-zull”? I’m not sure if that’s what you already meant by “xl” – that’s an ambiguous way of describing a sound.
roryokane | 17 hours ago
“Jay-eks-ell”, pronouncing each letter, feels most natural to me. Just like I call PNG files “pee-en-jee”. At three syllables, it’s longer than some other proposed options, but I’m not sure if any shorter pronunciation will become widely known.
DustyFuzzy | 14 hours ago
Going to start pronouncing PNG like pung now. (I expect this to lead to a meeting with HR, given that I'm Swedish)
objectiveryan | 8 hours ago
The pronunciation doesn't have to be anglocentric. See https://en.wikipedia.org/wiki/J#Use_in_writing_systems for inspiration. There are several more dimensions of bike shedding to explore!
My personal preference would be to interpret
jxas the Esperanto letterĵ(see https://en.wikipedia.org/wiki/Substitutions_of_the_Esperanto_alphabet#X-system for why), and readjxlas the two lettersĵandl, whose names are pronounced in sequence as /ʒo-lo/