Hacker News Reader

scorpio241on JPEG XL exceeds 20% of served images

Apple was always very frugal regarding memory and storage

scorpio241on JPEG XL exceeds 20% of served images

From discussion https://boards.4chan.org/g/thread/99659945/jpeg-xl-won

Recent benchmarks (crushing JPEG, WebP, AVIF): https://cloudinary.com/blog/jpeg-xl-and-the-pareto-front

scorpio241on Still no love for JPEG XL: Browser maker love-in snubs next-gen image format

After Adobe and Apple, also Samsung has recently started support (with S24): https://news.ycombinator.com/item?id=39064820

scorpio241on Samsung Joins Apple and Adobe in Supporting JPEG XL

Allowing to write as JPEG XL comes with necessity to read it - probably leading to full support.

Also they have a separate JPEG XL article: https://r2.community.samsung.com/t5/CamCyclopedia/JPEG-XL-Im...

scorpio241on Samsung Joins Apple and Adobe in Supporting JPEG XL

> Google's decision to deprecate JPEG-XL emphasizes the need for browser choice and free formats

https://www.fsf.org/blogs/community/googles-decision-to-depr...

scorpio241on What's the smallest file size for a 1 pixel image?

Here he writes https://twitter.com/jonsneyers/status/1378055527771602945

> a single pixel jxl image is 19 to 20 bytes depending on the color

scorpio241on Speed and Size Tests of JPEG XL on Apple Safari

Copy&pasted from https://old.reddit.com/r/jpegxl/comments/17o43g2/ran_a_few_s... :

Apple now supports JPEG-XL (a.k.a. JXL) in iOS 17, MacOS 14, and Safari!

This makes me happy, because I'm interested in JPEG-XL for its lossless compression as a replacement for PNG. To test it, I converted a few hundred images and compared...

Total file sizes (gigabytes):

7.93 — PPM (lossless, uncompressed)

1.97 — PNG (lossless, compression=9/9)

1.59 — JXL (lossless, effort=1/9)

1.37 — JXL (lossless, effort=3/9)

1.22 — JXL (lossless, effort=5/9)

1.15 — JXL (lossless, effort=7/9)

1.12 — JXL (lossless, effort=9/9)

1.02 — JPG (near-lossless, quality=100/100)

Total compression times (seconds):

1876 — PNG (lossless, compression=9/9)

28 — JPG (near-lossless, quality=100/100)

11 — JXL (lossless, effort=1/9)

107 — JXL (lossless, effort=3/9)

1802 — JXL (lossless, effort=5/9)

6651 — JXL (lossless, effort=7/9)

98506 — JXL (lossless, effort=9/9)

Total decompression times (seconds):

76.2 — PNG (lossless, compression=9/9)

17.7 — JPG (near-lossless, quality=100/100)

21.2 — JXL (lossless, effort=1/9)

98.0 — JXL (lossless, effort=9/9)

Conclusions:

    Lossless JXL is damn good. Even on its lowest-effort setting, it can improve on PNG's best-case file size by 25%, while doing so 150 times faster. This alone is a big win. On its highest-effort setting (much slower), JXL completely blows PNG out of the water with files about half the size.

    Lossless JXL file sizes can be almost as tiny as the best quality lossy JPEG, if you've got CPU cycles to dedicate.

    Lossless JXL's "compression effort" setting has a much larger impact on elapsed time than it does on file size. Setting effort=9 results in files 70% the size of effort=1, but takes 7000 times longer. Effort settings above 7 (the default) aren't probably worth it. Setting effort=9 costs 15x more time than effort=7 for only 1% to 2% reduction in file size.

    If you're looking for a blazingly fast PNG replacement, try JXL in lossless mode with effort=1.

Tools used for the test:

    netpbm (pnmtojpeg, jpegtopnm, pnmtopng, pngtopnm)
    libjxl (cjxl, djxl)

scorpio241on 4 months later, Chrome still hasn't changed its opinion about supporting JPEG XL

https://foolip.github.io/interop-reactions/ This is a list of Interop 2024 proposals sorted by number of reactions - JPEG XL definitely wins

scorpio241on Google's decision to deprecate JPEG-XL emphasizes the need for browser choice

Also Thorium: https://thorium.rocks/

scorpio241on JPEG-XL vs. AVIF and Others: 27 Images Compared

This is a battle for future default image codec: open standard vs nearly proprietary controlled by a few corporations - https://en.wikipedia.org/wiki/Alliance_for_Open_Media : > The governing members of the Alliance for Open Media are Amazon, Apple, ARM, Cisco, Facebook, Google, Huawei, Intel, Microsoft, Mozilla, Netflix, Nvidia, Samsung Electronics and Tencent.

For example with defensive license termination: they can sue you, but if you try to sue them you have to rip off AVIF from all your products: https://aomedia.org/license/patent-license/

>Defensive Termination. If any Licensee, its Affiliates, or its agents initiates patent litigation or files, maintains, or voluntarily participates in a lawsuit against another entity or any person asserting that any Implementation infringes Necessary Claims, any patent licenses granted under this License directly to the Licensee are immediately terminated as of the date of the initiation of action unless 1) that suit was in response to a corresponding suit regarding an Implementation first brought against an initiating entity, or 2) that suit was brought to enforce the terms of this License (including intervention in a third-party action by a Licensee).

scorpio241on Mozilla concludes that JPEG-XL is not for them

Top of Mozilla trending: "Support JPEG XL" with 328 upvotes ...

https://connect.mozilla.org/t5/ideas/idb-p/ideas/status-key/...

They are ignoring their users ... wonder why they are leaving

scorpio241on Asymmetric numeral systems – A new approach to accurate entropy coding (2014) [pdf]

And many others: https://en.wikipedia.org/wiki/Asymmetric_numeral_systems

>Among others, ANS is used in the Facebook Zstandard compressor[6][7] (also used e.g. in Linux kernel,[8] Android[9] operating system, was published as RFC 8478 for MIME[10] and HTTP[11]), Apple LZFSE compressor,[12] Google Draco 3D compressor[13] (used e.g. in Pixar Universal Scene Description format[14]) and PIK image compressor,[15] CRAM DNA compressor[16] from SAMtools utilities,[17] Dropbox DivANS compressor,[18] Microsoft DirectStorage BCPack texture compressor,[19] and JPEG XL[20] image compressor.

scorpio241on JPEG XL support has officially been removed from Chromium

There was some discussion about this rANS patent among data compression experts, but it looked like they don't know what improvement it is supposed to bring:

https://encode.su/threads/3863-RANS-Microsoft-wins-data-enco...

scorpio241on JPEG XL support has officially been removed from Chromium

Not used anywhere? E.g. Affinity Photo has support for JPEG XL, but not for AVIF. Not used in browsers because they are nearly controlled by Chromium, which is clearly biased toward AVIF. https://en.wikipedia.org/wiki/JPEG_XL#Official_support Official support:

    Squoosh – In-browser image converter[42]
    Adobe Camera Raw – Adobe Photoshop's import/export for digital camera images[43]
    Affinity Photo – raster graphics editor[44]
    Chasys Draw IES – raster graphics editor[45]
    Darktable – raw photo management application[46]
    ExifTool – metadata editor[47]
    FFmpeg – multimedia framework, via libjxl[48]
    GIMP – raster graphics editor[49]
    gThumb – image viewer and photo management application for Linux[50]
    ImageMagick – toolkit for raster graphics processing[51]
    IrfanView – image viewer and editor for Windows[52]
    KaOS – Linux distribution[53]
    Krita – raster graphics editor[54][55]
    libvips – image processing library[56][57]
    vipsdisp – high-performance ultra-high-resolution image viewer for Linux[58]
    Qt and KDE apps – via KImageFormats[59]
    XnView MP – viewer and editor of raster graphics[60]
    Pale Moon – web browser[61]

scorpio241on Microsoft forked MIT licensed repo and changed the copyright [fixed]

Here in "honest mistake" they try to patent somebody's method: https://www.theregister.com/2021/03/13/microsoft_ans_patent/

scorpio241on Poland's oldest university denies Google's right to patent Polish coding concept

The patent application clearly contains concepts from their discussion with Duda, which they didn't disclose while applying, but was pointed by ISA reviewer: https://register.epo.org/application?documentId=EZ46ZRSY2014...

ps. hot today reddit: https://www.reddit.com/r/programming/comments/6uuqcd/google_...