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

31–40 of 93 posts

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

#31

Post by Gigachad »

201984 wrote: post #29
Gigachad wrote: post #28

Earlier quoted context omitted.

It's an open standard because the concepts and reference implementation are free and open source even if the PDF is paywalled. Realistically you could just pirate the PDF and write a jpeg xl encoder/decoder and your code wouldn't be infringing on any patents.

Seems "closed but royalty free" would be a more accurate description then.

Splitting hairs on terminology I guess. Very few people are interested in the PDF that specifies the format vs being able to include decoders in software and on devices without paying a royalty for every device. There are alternative documents and the last draft copy which are free legally. As well as the reference code.

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

#32

Post by jazzyjackson »

markdog12 wrote: post #11
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.

Came here to say the same thing. Why add this fake image?

Website Obesity mentioned ! [0]

  This project led me to propose the Taft Test:

  Does your page design improve when you replace every image with William Howard Taft?

  If so, then, maybe all those images aren’t adding a lot to your article. At the very least, leave Taft there! You just admitted it looks better.
[0] (idlewords.com/talks/website_obesity): https://web.archive.org/web/20260421022440/https://idlewords...

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

#33

Post by aidenn0 »

201984 wrote: post #27

Mostly off topic, but why is the spec for JPEG and JPEG XL paywalled? I wouldn't call them open standards if they're not available free-of-charge to the public.

"Open Standard" means "Anybody is allowed to buy it"

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

#35

Post by mceachen »

_HMCB_ wrote: post #34

Google spearheaded this and yet their browser only has experimental support? While Safari shipped it in 2023? At least, that’s how I’m reading this.

It's worse: Google added and then dropped even experimental support of jxl in 2021-2022. Several years later they adopted the rust jxl library, but have kept it behind experimental flags.

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

#36

Post by threatripper »

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…

This is why we need smart glasses recording everything you see 24/7 to gather relevant real training data.

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

#37

Post by fc417fc802 »

magicalist wrote: post #6
rowbin wrote: post #2

That's rich coming from the company that tried to kill it. The audacity...

> 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.

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

#38

Post by taikahessu »

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"?

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

#39

Post by ZeroGravitas »

201984 wrote: post #27

Mostly off topic, but why is the spec for JPEG and JPEG XL paywalled? I wouldn't call them open standards if they're not available free-of-charge to the public.

It's a standard ISO Standard thing which could perhaps be justified when standards where printed on paper.

The JPEG XL team released a draft to try to work around this but couldn't avoid it for the official standard release.

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

#40

Post by gforce_de »

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...

Post reply on HN