Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Can someone comment on what is newsworthy about this?


JPEG XL is alive despite google trying their best to kill it and is used to treat cancer


Google Research was central in developing and continuing to push JPEG XL.

The Google Chrome folks are the ones who decided to disallow it. You could argue that they are trying to kill it, but certainly not Google at large.


Someone using JPEGXL in a real world product


jpegxl is supported by pretty much every relevant program that deals with images. The web situation is purely because of Google's monopoly.


But exceedingly few cameras (this is the only one I'm aware of). If I had to guess it's probably encoding in software but still, it's a start.


There has to be someone else since my dad just emailed me a JPEGXL image less than 15 minutes ago. No idea on how he produced or procured it.


A medical device that outputs a standard image format instead of proprietary garbage


The cluster fuck that is DICOM and HL7 once vendors go to town is far from the ‘open’ utopia we dream of.


Basically there is a conspiracy theory that google is trying to kill jpeg xl, so the anti-google crowd is excited someone is using it.

The truth is that every image format added to a web browser has to be supported forever, so chrome team is wary of adding new file formats unless its an above and beyond improvement. Jpeg XL isn't (relative to avif) so google decided not to implement. Its not some malicious conspiracy, it just didn't make sense from a product perspective.

From what i understand https://storage.googleapis.com/avif-comparison/index.html is what was used to justify google chosing avif over jpeg-xl. Jpeg-xl was better at lossless images but avif was better at lossy, and lossy is the usecase that matters more to the web.


nerds desperately clinging to any hope that jpeg xl will be revived


Nerds like JPEG XL but Google is trying to kill it.


Why does it try to kill it ?


Because they can't control it


hardly, it's a google team that made the thing.


Then why does Google not want JPEG XL support in Chrome?


Google is not a monolith. The Chrome team doesn't want it in Chrome, but many other parts of Google likes it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: