Running JPEG-XL tools on shared Dreamhost

https://www.phpied.com/running-jpeg-xl-tools-on-shared-dreamhost/ by @stoyan

#WebPerf #ImagePerf #JPEGXL #JXL

FFmpeg unterstützt jetzt animierte JPEG-XL Bilder

Bei der Unterstützung des JXL-Formats gibt es, insbesondere bei den Webbrowsern, kein klares Bild. Durch Apples Ja zum Bildformat für Safari und die erweiterte Unterstützung durch FFmpeg, ändert sich die Situation eventuell.

#JXL #JPEG_XL #Ffmpeg #animiert #Linux

https://gnulinux.ch/ffmpeg-animierte-jpeg-xl-bilder

I was playing with #jxl today, and I found this settings gave me the best results at a reasonably fast speed:

cjxl -e 8 SOURCE JXLfile.jxl

#JXR & #JXL & #WebP2
JXR이 마이크로소프트가 만든 규격이라 오픈 소스 커뮤니티에 인기가 없나보다.
오픈소스 커뮤니티가 밀던 JXL은 함께 개발한 구글이 버리고 WebP 2로 갔나보다.
마이크로서프트와 엔비디아가 HDR 스크린샷은 JXR로 찍어주기 시작하면서 대중의 로컬에는 HDR 스크린샷이 잔뜩 쌓이고 있다.
오픈 소스 커뮤니티는 JXR 그것은 아무것도 아니라며 JXL 얘기한다. 크롬은 둘 모두 미지원이다.
#HDR 쓰지 말란 얘기지?

#JXR & #JXL & #WebP2
JXR이 마이크로소프트가 만든 규격이라 오픈 소스 커뮤니티에 인기가 없나보다.
오픈소스 커뮤니티가 밀던 JXL은 함께 개발한 구글이 버리고 WebP 2로 갔나보다.
마이크로서프트와 엔비디아가 HDR 스크린샷은 JXR로 찍어주기 시작하면서 대중의 로컬에는 HDR 스크린샷이 잔뜩 쌓이고 있다.
오픈 소스 커뮤니티는 려더외 JXR은 아무것도 아니라며 JXL 얘기한다. 크롬은 둘 모두 미지원한다.
#HDR 쓰지 말란 얘기지?

#JXR & #JXL & #WebP2
JXR이 마이크로소프트가 만든 규격이라 오픈 소스 커뮤니티에 인기가 없나보다.
오픈소스 커뮤니티가 밀던 JXL은 함께 개발한 구글이 버리고 WebP 2로 갔나보다.
마이크로소포스트와 엔비디아가 HDR 스크린샷은 JXR로 찍어주기 시작하면서 대중의 로컬에는 잔뜩 쌓이고 있다.
오픈 소스 커뮤니티는 JXR은 아무것도 아니라며 JXL 얘기한다.
HDR 쓰지 말란 얘기지?

Waiting for Safari 17 to test the PostCSS plugin to use JXL in the CSS background

https://github.com/nucliweb/jxl-in-css

#JPEGXL #JXL #PostCSS #CSS #ImagePerf #ProductPerf #WebPerf

(Possibly relevant the fact that new version of Safari and their toolkit web view components are going to support #HEIC together with #JXL.)

And you know what? I'll take it. As self-serving as the choice may be, if it helps the new open standard gain traction, I'll take it, especially considering how often things go the other way instead. Surely better than Google's braindead choice to pull the implementation they had already added to #Blink.

4/

I don't believe #Apple's choice to adopt #JpegXL is a selfless embracement of open standards. Rather, I suspect they ran internal tests and found out quickly that #jxl allowed them for sufficiently more compact files (better for storage and transmission) and faster deciding for their own purposes to justify its adoption. I wouldn't be surprised if they start phasing out #HEIC in favor of JXL as their photo format as a next step.
3/

I'm generally not a big fan of #Apple (understatement of the century), but I've read about the next version of #Safari officially supporting #JpegXL and I'm really glad that this is happening. I'm looking forward to the associated changes to #WebKit making it into the engine as it is used by other #FLOSS browsers too —and hopefully this will finally push @Mozilla into enabling #jxl in mainline #Firefox OOTB.
1/

@stshank #jpegxl #jxl FTW 😉

I just realized that #Google killing #JpegXL has a direct negative impact on the #Fediverse, by imposing higher bandwidth and storage requirements for anyone hosting media. Platforms like #PixelFed in particular would greatly benefit from being able to transcode everything to #jxl for storage (with no additional loss of quality thanks to the possibility to transcode directly from #jpeg in most cases), reducing storage and bandwidth by 10% or more, easily.

While I agree with the @fsf warning about the emblematic value of the decision by #Google to pull support for #JpegXL from #Chrome, their article <https://u.fsf.org/3z8> is as empty as could be, _especially_ considering that #GNU #IceCat doesn't support JPEG XL either (being based on a #Firefox branch that doesn't build #JXL support in.) You want to show that #FLOSS can do without? Do it by actually supporting what you complain Google is failing to.

This has been one of the most amazing and informative threads I've ever participated in.

https://disobey.net/@gianni/110184072335118737

#JPEG #JXL #JPEGXL #Photo #Compression

@koolinus @leodurruti

These are shiny cool things, but in the end nobody really cares, since it takes 0.5 seconds more to open in a program suited to edit #PDF s.

WE WANT #JpegXL! That would make a difference.

#JXL #Firefox

@werefox honestly Google seems to be fighting quite hard against #JXL, trying to promote WebP and AVIF instead. For example, they recently removed JXL support from chromium, for no reason and despite even their own engineers protesting. Which is yet more reason to favour JXL.

@werefox yeah legit and maybe I should have elaborated too. but basically for the readers at home, #JXL is just existing formats but better, and that includes #WebP. It's also extremely future proof, so if it gets widely adopted we can probably expect it to still be in use in >10 years time. AND it's royalty free and completely open source!

JPEG XL: #Mozilla #Firefox ist neutral – und bald auch egal | heise online https://www.heise.de/meinung/Kommentar-Mozilla-geht-neutral-einen-weiteren-Schritt-Richtung-irrelevant-7493700.html #saukontrovers #JXL #jpegXL

Firefox joins Chrome and drops support for the new JPEG-XL image format

https://github.com/mozilla/standards-positions/issues/522#issuecomment-1409539985

#Image #ImagePerf #JPEGXL #JXL

If their web browser also adopts a superior image format in its native mode, it will make many to consider switching to Windows 11 … #jpegxl #jxl https://www.theverge.com/23589994/microsoft-ceo-satya-nadella-bing-chatgpt-google-search-ai