News for hackers. Stuff that matters.
Re:Philips announces digital pathology scanner with native D... by avalys on Saturday September 20, 2025 @04:28PM (#45317149)
Can someone comment on what is newsworthy about this?
Re:Philips announces digital pathology scanner with native D... by kiicia on Saturday September 20, 2025 @04:31PM (#45317188)
JPEG XL is alive despite google trying their best to kill it and is used to treat cancer
Re:Philips announces digital pathology scanner with native D... by Caspy7 on Monday September 22, 2025 @11:40PM (#45342597)
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.

Re:Philips announces digital pathology scanner with native D... by kangalioo on Saturday September 20, 2025 @04:30PM (#45317174)
Someone using JPEGXL in a real world product
Re:Philips announces digital pathology scanner with native D... by ndriscoll on Saturday September 20, 2025 @04:55PM (#45317428)
jpegxl is supported by pretty much every relevant program that deals with images. The web situation is purely because of Google's monopoly.
Re:Philips announces digital pathology scanner with native D... by daemonologist on Saturday September 20, 2025 @07:35PM (#45318594)
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.
Re:Philips announces digital pathology scanner with native D... by Hamuko on Saturday September 20, 2025 @05:08PM (#45317563)
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.
Re:Philips announces digital pathology scanner with native D... by arccy on Saturday September 20, 2025 @05:51PM (#45317912)
nerds desperately clinging to any hope that jpeg xl will be revived
Re:Philips announces digital pathology scanner with native D... by ThrowawayTestr on Saturday September 20, 2025 @04:30PM (#45317183)
A medical device that outputs a standard image format instead of proprietary garbage
Re:Philips announces digital pathology scanner with native D... by lostlogin on Saturday September 20, 2025 @05:18PM (#45317655)
The cluster fuck that is DICOM and HL7 once vendors go to town is far from the ‘open’ utopia we dream of.
Re:Philips announces digital pathology scanner with native D... by UltraSane on Saturday September 20, 2025 @04:33PM (#45317206)
Nerds like JPEG XL but Google is trying to kill it.
Re:Philips announces digital pathology scanner with native D... by makapuf on Saturday September 20, 2025 @04:54PM (#45317416)
Why does it try to kill it ?
Re:Philips announces digital pathology scanner with native D... by greenavocado on Saturday September 20, 2025 @04:55PM (#45317430)
Because they can't control it
Re:Philips announces digital pathology scanner with native D... by arccy on Saturday September 20, 2025 @05:50PM (#45317903)
hardly, it's a google team that made the thing.
Re:Philips announces digital pathology scanner with native D... by UltraSane on Sunday September 21, 2025 @09:09AM (#45322401)
Then why does Google not want JPEG XL support in Chrome?
Re:Philips announces digital pathology scanner with native D... by lonjil on Sunday September 21, 2025 @09:50AM (#45322731)
Google is not a monolith. The Chrome team doesn't want it in Chrome, but many other parts of Google likes it.
Re:Philips announces digital pathology scanner with native D... by bawolff on Saturday September 20, 2025 @09:03PM (#45319101)
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.