JyrkiAlakuijala

6 ms·

1. 31.▲
   by JyrkiAlakuijala 1y ago

   > killed off my guesswork is that JPEG XL will likely outlive Chrome by 100+ years
2. 32.▲
   by JyrkiAlakuijala 2y ago

   Lossy compression can be megabytes vs. tens or hundreds of megabytes per image kind of question, i.e., worth all the sweat it brings.
3. 33.▲
   by JyrkiAlakuijala 2y ago

   ZSTD/Tiff is quite far from JPEG XL in compression density. There are many technical reasons why this is the case.
4. 34.▲
   by JyrkiAlakuijala 2y ago

   I believe JPEG XL allows different scaling per layer, including decent default interpolation. But usually exotic things are easier to engineer if you do them outside of the container, then you don't need to figure out how the standard
5. 35.▲
   by JyrkiAlakuijala 2y ago

   While DNG uses JPEG XL internally for great compression, its implementation sacrifices some of JPEG XL's inherent advantages. For instance, JPEG XL's progressive rendering and preview capabilities are lost within the DNG containe
6. 36.▲
   by JyrkiAlakuijala 2y ago

   Thank you for such a kind praise for Jpegli! This made my day.
7. 37.▲
   by JyrkiAlakuijala 2y ago

   JPEG XL is seeing strong industrial adoption where image quality matters: professional and prosumer image acquisition (as a replacement, with huge benefits, of traditional raw imaging in iPhone 16 Pro) and processing and storage reduction w
8. 38.▲
   by JyrkiAlakuijala 2y ago

   MozJPEG encoding times are not that great but decoding is still fast. I believe with Jpegli you can have faster encoding than with MozJPEG.
9. 39.▲
   by JyrkiAlakuijala 2y ago

   Thank you! This news gave me goosebumps-of-delight for three hours or so :-D
10. 40.▲
    DICOM Medical Image Standard Chooses JPEG XL as a Payload Codec [pdf](dicomstandard.org)

    19 points by JyrkiAlakuijala 2y ago|4 comments
11. 41.▲
    by JyrkiAlakuijala 2y ago

    DICOM 2024d version published today uses JPEG XL for coding images. It supports JPEG XL completely: lossless, JPEG1 recompression and lossy, including multichannel. This can reduce archiving costs, speed up operation, improve image quality
12. 42.▲
    by JyrkiAlakuijala 2y ago

    Use Jpegli for now. You can get half the benefits of JPEG XL with it.
13. 43.▲
    by JyrkiAlakuijala 2y ago

    They might have some things like DCTs and colorspace transforms accelerated.
14. 44.▲
    by JyrkiAlakuijala 2y ago

    I will buy an iphone if it supports jpeg xl, and exactly because of that reason. ProRAW or DNG on top of jpeg xl, I wouldn't buy yet...
15. 45.▲
    by JyrkiAlakuijala 2y ago

    Agreed. At camera quality jpeg xl is far ahead in quality. Apple's last announcement is about camera quality, close to lossless kind of lossy. In this domain jpeg xl does not have real competition. AVIF and HEIC don't even support
16. 46.▲
    by JyrkiAlakuijala 2y ago

    I don't know, but my guesswork is that the DNG/ProRAW/JXL support comes with compatibility challenges. Limiting the size of the launch to well-informed photography prosumers and professionals will help to iron out the compati
17. 47.▲
    by JyrkiAlakuijala 2y ago

    My take on this is that junior engineers optimize for the cpu as it is easy to measure, senior engineers for the user experienced latency as it matters more. Users know that their time is valuable. If your website is fast, they will explore
18. 48.▲
    by JyrkiAlakuijala 2y ago

    Could it be improved by having a wrapper for simple uses?
19. 49.▲
    by JyrkiAlakuijala 2y ago

    https://news.ycombinator.com/item?id=41443336 has more comments
20. 50.▲
    by JyrkiAlakuijala 2y ago

    https://news.ycombinator.com/item?id=41443336 has more comments
21. 51.▲
    by JyrkiAlakuijala 2y ago

    Personally, I'm on the edge on this one. I think both viewpoints are valid. One way to think of Highway is that it is portable multi-platform SIMD intrinsics for C++. While we developed it originally as a part of JPEG XL, it has long a
22. 52.▲
    by JyrkiAlakuijala 2y ago

    great analysis and summary of the JPEG XL benefits!
23. 53.▲
    by JyrkiAlakuijala 2y ago

    I believe that there are already several decoder implementations that pass the ISO conformance test for JPEG XL. I don't remember which one's exactly but I believe at least both jxl-oxide and libjxl do.
24. 54.▲
    by JyrkiAlakuijala 2y ago

    and that 38 kloc includes the encoder, psychovisual model, etc. etc. that are not needed for the decoder current decoder is around 20 kloc
25. 55.▲
    by JyrkiAlakuijala 2y ago

    I believe that analysis is unfair or imprecise libjxl decoder is 3-5x smaller in binary and 10x smaller in specification text size than an avif decoder
26. 56.▲
    by JyrkiAlakuijala 2y ago

    Zilog Z80: The reports of my death are greatly exaggerated. I'm actually creating life nowadays.
27. 57.▲
    by JyrkiAlakuijala 3y ago

    I was very careful not to overstate WebP lossless quality. I compressed the originals with zopflipng and pngcrush before stating figures (-26 %). If I had just used the internet quality images, WebP lossless would have improved size by -42
28. 58.▲
    by JyrkiAlakuijala 3y ago

    I don't think that is accurate. Brotli was added first to Firefox. It took 9 months longer for Chrome. Brotli has many other uses than content encoding in the web.
29. 59.▲
    by JyrkiAlakuijala 3y ago

    Fun fact -- gemma.cpp uses highway, an amazing high performance computation library originally developed in the JPEG XL effort.
30. 60.▲
    by JyrkiAlakuijala 3y ago

    Thank you! This is comforting to know!