Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Journey to JPEG XL: open-source experiments shaped the future of image coding

opensource.googleblog.com

Post reply on HN
Print view View original

41–50 of 93 posts

Re: Journey to JPEG XL: open-source experiments shaped the future of image coding

#41

Post by qingcharles »

fc417fc802 wrote: post #37
magicalist wrote: post #6

Earlier quoted context omitted.

> That's rich coming from the company that tried to kill it This post is written by three of the authors of the JPEG XL spec, implementors of the reference and rust implementations of libjxl, and...longtime google employees.

You say that as though Google isn't notorious for killing their own successful and well received products for seemingly no reason. It's incontrovertible that Google did attempt to kill browser adoption of jxl at one point. Thankfully they seem to have reversed course.

They only reversed under pressure from the Safari and Firefox folks.

The killing of JXL did push the ever-talented Jyrki to create jpegli, which was honestly a wonder.

Re: Journey to JPEG XL: open-source experiments shaped the future of image coding

#42

Post by qingcharles »

gforce_de wrote: post #40
taikahessu wrote: post #38

Can someone explain where are we at the image processing world/timeline? Why do coding tools suggest to me .avif and .webp, and the support of these lags in Windows OS and then we have things like JpegXL and Jpeg2000 or whatever others are there flying around? Why is it so hard to find our next "jpg format"?

It's all about licences. If you need the images for the web: go for jpegli, webp and avif - the distance to jpegxl or webp2 is not worth the hassle: https://show.quicky.club/results/14/f8/f1/d8db84d57222d32db6...

Agree. JXL won't be baseline for at least three years.

Re: Journey to JPEG XL: open-source experiments shaped the future of image coding

#43

Post by pezezin »

bnolsen wrote: post #22

I personally think something like the qok format is a better way to go. Make something that performs well and is dirt simple to implement.

QOI is cute as an experiment, but it is not a serious image format unless you work in extremely constrained environments.

Re: Journey to JPEG XL: open-source experiments shaped the future of image coding

#44

Post by Gigachad »

taikahessu wrote: post #38

Can someone explain where are we at the image processing world/timeline? Why do coding tools suggest to me .avif and .webp, and the support of these lags in Windows OS and then we have things like JpegXL and Jpeg2000 or whatever others are there flying around? Why is it so hard to find our next "jpg format"?

AVIF and webp kind of only exist for the web, they get used when you want to really crunch down on data as much as possible. They aren’t really used for files you’d save on your computer or get out of a camera.

JPEG XL is replacing regular jpeg and heif for photography. It offers 16 bit color rather than 8 from jpeg and HDR support along with a ton of extra features.

Every OS but Android supports it, safari supports it, chrome and Firefox have it behind a beta flag.

Re: Journey to JPEG XL: open-source experiments shaped the future of image coding

#46

Post by halapro »

Gigachad wrote: post #18
rowbin wrote: post #3

Earlier quoted context omitted.

> Safari (2023) led among major browsers, while Firefox and Chrome currently maintain experimental support.

Maintain in a sense. Google introduced it in Chrome as an experimental flag, then removed it with no real explanation, and only just brought it back.

Which it makes perfect since this it's the same company which "deprecated" MP4 support a long while ago in an effort to push to WebM.

Re: Journey to JPEG XL: open-source experiments shaped the future of image coding

#47

Post by breppp »

mrandish wrote: post #30
Mindless2112 wrote: post #7

> In this Gemini-reconstructed scene, ... I'm generally pretty pro-AI, but I find this icky. Of course, I wouldn't have noticed except the whiteboard drawing seemed not quite right, so I'll probably be fooled in the future.

Yep, I was totally nerd-sniped by the image. I've never seen an engineer draw a whiteboard diagram anywhere near that detailed and tidy. No acronyms, consistent title case, descenders on a baseline - everything about it is wrong. It's so counter to reality, I seriously wondered if it was a joke. The Nano Banana team should be pissed Google PR is distributing such a terrible photo. The poses are stilted, expressions f…

I think the logic follows: If we are already staging a scene just for PR purposes as was usually done then why not generate it using AI?

Re: Journey to JPEG XL: open-source experiments shaped the future of image coding

#48

Post by breppp »

Gigachad wrote: post #17

Huge fan of JXL, but this article feels pretty AI sloppy. Not much said here, coming from the google blog I was hoping for some news about how they are pushing the format forward by introducing decoders in to Android and enabling on Chrome. Android is the only mainstream OS that does not support JPEG XL right now.

I initially read the articles without images (they don't load for an unrelated reason) and actually felt it gave a good summary of JPEGXL underlying technologies and history, I also learned some new stuff.

I think the images might give a slop framing which is undue

Re: Journey to JPEG XL: open-source experiments shaped the future of image coding

#49

Post by apt-get »

The sloppa in this article is... offending.

The obvious AI headings, pointless genned image of people (I'm starting to think islam had a point with discouraging depictions of human figures), and especially the blurry, artifacted, distractingly skeuomorphic diagram, with random wire traces going everywhere... this is a technical blog, not an investor sales pitch! Every time I see one of these, I have to double-check for a second if I'm not on some phishing SEO site!

If even Google, previously a gold standard of technical writing, is falling prey to this kind of laziness, then I have nothing to worry about -- knowing how to write without a language model in the driver's seat is gonna be a top tier skill in the future...

A damn shame too, as I've been following the progress of JXL in the standardization pipeline for a few years now and was quite interested in the historical breakdown, but all that's gonna stick with me from this is the disrespect I felt as a reader.

Re: Journey to JPEG XL: open-source experiments shaped the future of image coding

#50

Post by arghwhat »

mrandish wrote: post #30
Mindless2112 wrote: post #7

> In this Gemini-reconstructed scene, ... I'm generally pretty pro-AI, but I find this icky. Of course, I wouldn't have noticed except the whiteboard drawing seemed not quite right, so I'll probably be fooled in the future.

Yep, I was totally nerd-sniped by the image. I've never seen an engineer draw a whiteboard diagram anywhere near that detailed and tidy. No acronyms, consistent title case, descenders on a baseline - everything about it is wrong. It's so counter to reality, I seriously wondered if it was a joke. The Nano Banana team should be pissed Google PR is distributing such a terrible photo. The poses are stilted, expressions f…

I have seen such detailed and tidy whiteboard diagrams, but the catch is that they never occur in active discussion. It doesn't make room for scribbling, and stopping a discussion for 5-10 minutes to draw slowly and nicely doesn't make sense...
Post reply on HN