HNHacker News
TopNewBestAskShowJobs

Broiler9437

26 karma · joined August 26, 2026

submissionscomments
Broiler9437··on Android apps running native on macOS
Cross-platform has never been easier than ever
Broiler9437··on JPEG XL vs. AVIF for web use-cases
JXL encoder is just very unoptimized, so lossy screenshot is currently pretty bad
Broiler9437··on JPEG XL vs. AVIF for web use-cases
Yes, with all metadata preserved. The converted JXL even has checksum metadata for verification
Broiler9437··on JPEG XL vs. AVIF for web use-cases
It's a lossless conversion while still saving spaces. You can even convert back to get the exact same file bit-perfect
Broiler9437··on JPEG XL vs. AVIF for web use-cases
Decoding support is pretty poor though. JXL decoder are much more friendly beyond 16K
Broiler9437··on JPEG XL vs. AVIF for web use-cases
AVIF doesn't work that great either. Let's just switch to AV1 video. AVIF animated still really buggy compared to the video itself
Broiler9437··on JPEG XL vs. AVIF for web use-cases
This is not jixel though. It was their own encoder
Broiler9437··on JPEG XL vs. AVIF for web use-cases
This is awesome. Thanks for sharing
Broiler9437··on Shipping JPEG XL in Chrome
Current encoder regressed a lot on lossy images compared to 0.7 era. There will be works done to fix this in near future
Broiler9437··on Shipping JPEG XL in Chrome
Definitely possible. The reference encoder has a lot of room to improve. Even for lossless there are things to improve too
Broiler9437··on Shipping JPEG XL in Chrome
Upload the source or it is just empty talk
Broiler9437··on Shipping JPEG XL in Chrome
16bit PNG is simply too inefficient. If you care about high bit depth, JXL has vastly higher 32 bit ceiling with superior compression
Broiler9437··on Shipping JPEG XL in Chrome
Hence them specifying creation tools. Even Adobe fuck up their JXL encode in some cases too
Broiler9437··on Shipping JPEG XL in Chrome
You must have mistaken somewhere, the decoder absolutely does support high bit depth
Broiler9437··on Shipping JPEG XL in Chrome
Webview generally follow Chrome as well. Both the versioning and update timing confirm this
Broiler9437··on Shipping JPEG XL in Chrome
Outside of special exeptions, Chrome Android always received the same feature updates as desktop. I just checked the source code and confirmed it does support JXL now
Broiler9437··on Shipping JPEG XL in Chrome
Quantized PNGs are a thing and those are not easily detected either. For JXL, most files compressed with Modular mode are lossless. You can detected them in the metadata
Broiler9437··on Shipping JPEG XL in Chrome
Definitely not with lossless. It consistently lose to JXL and WebP
Broiler9437··on Shipping JPEG XL in Chrome
Being a well supported format on all OSs will allow that. One of the biggest failure of WebP was very poor native support beyond browsers. JXL is supported natively by pretty much all operating systems right now beside Android. JPEG recompression is simply an advantage
Broiler9437··on Shipping JPEG XL in Chrome
It looks fine sure, but that doesn't make it good either. Are you going to lock display technology to 8 bit forever? Most PC monitors already match or exceeding that limit, phones especially. HDR is something that needs to happen eventually, and for that new format is very important
Broiler9437··on Shipping JPEG XL in Chrome
I mean we are already dealing with that nowadays. Many PNGs are either JPEG in a different package or straight up lossy compressed. Unfotunately extensions have never been safe for judge
Broiler9437··on Shipping JPEG XL in Chrome
Art sites get the biggest gain with JXL. They can losslessly repackage every single JPEG uploads they have for practically zero cost. Existing PNG can also be losslessly compressed to JXL too, and just wrapping JXL around PNG yields improved compression (Note for last part: it is still in proposal status)
Broiler9437··on The case against JPEG XL
Google Photo teams wanted JXL too, but had to hold back due to Chromium not supporting them
Broiler9437··on The case against JPEG XL
I have no issue with EXIF here. Compressed JPEGs were reverted with zero data lost