/g/ - Technology

>>fg-3T1IXMQU (OP) Hijacking this thread to mention that posting webp images doesn't work

>>fg-6M6I8V3O Can also confirm that webp doesn't work either.

NSFW Content

Can JPEG XL be enabled now that even current ungoogled-chrome has support for it built-in ( chrome://flags/#enable-jxl)? Supported browsers: https://www.caniuse.com/jpegxl Also requested was webp, posted this on /g/ before I saw meta >>fg-3T1IXMQU (OP)

>>fg-3T1IXMQU (OP) What is this "JPEG Xl"?

>>fg-RT5KQNKG The most efficient image format that is practical to use. This was ~2MB as PNG, now it's ~1MB as JXL. Lossless: https://files.shittyurl.org/z4izory7.jxl If you haven't JXL support enabled in your browser yet, download and feed it into https://squoosh.app/ instead. But if fchan allowed the format, we could directly shitpost with jxl.

NSFW Content

>>fg-3T1IXMQU (OP) JPEG-XL

NSFW Content

>>fg-F4X08QL1 avif in real world usage offers better compression ratios compared to jxl, even if the avif encoder is slow as balls. in overall usage (as well as niche professional use cases) id still give jxl the win considering that the encoder is much faster. but for the benefit it offers to people who need to encode, jxl is unduly cuntish to passive consumers who must decode images. i have a massive booru collection ive encoded to both avif and jxl formats, but decoding jxl is more taxing than avif to the extent that dolphin (which i assume is doing something stupid like regenerating thumbnails) spikes the cpu usage to 100 each time the jxl folder is opened, but not on the avif folder. i havent rigorously tested or compared the time it takes to open images in gwenview (its usually negligible for both avif and jxl) but on the really high resolution images it sadly takes many seconds to decode the image (both on avif and jxl) when png or jpg is almost instantaneous. ymmv, im on a core2duo so something made in the last decade may have better results

I filesize-dropped my large images to WEBP. WEBP offers mature codec, storage savings, and speed, now as of 2021. AVIF is the next advanced open digital image format, but it is not ready for production until 2023+

Make your images smaller, and then you don't need these new google formats. There is always a tradeoff with compression and complexity/CPU usage. Google (a CIA nigger front company) wants you locked-in to the modern botnet hardware, whereas GIF and JPG were good enough in the dialup era, so long as the webmaster wasn't a retard.

>>fg-PRN4Y7FZ WEBP is very open, and AVIF will be more supported. Neither are botnet hardware formats, you are mistaken. Also, wrong, in many ways. JXL will be a botnet format. It is proprietary from MPEG, who authored JPEG, and that simply has more ubiquitous decoding now, which is why you probably see it as good, yet forget who authored it. Your entire paragraph has multiple different logics to it. Stop posting.

Are you fucking retarded? I only talked about CPU usage. I don't care if it's "open" (legally) or not. Google is pushing for more complicated code that has more overhead, so it won't run as well on older CPUs (the only ones that aren't full botnet).

>>fg-ONTMUJ82 You absolutely failed to specify what the CPU connection was to the format, you are retarded, and a failed, unclear communicator. In addition, your concern is absolute bullshit, talking out of your ass bullshit, because you havent even tested a decode, because you also failed to mention the details of that. So, get fuckin real. You want to run old hardware and whine about significant compression progress,which could result in 25-50% image storage savings and consequently page loading speed, instead of devising a solution for your setup. Not my fault youre some poorfag to his desires that cant afford two boxes and doesnt know how to run a batch image converter. Real fucking intelligence. Shut the fuck up and figure it out for yourself, its your fucking problem anyway. And voilà: Retard. - "AVIF Image Support The AV1 Image File Format (AVIF) is a powerful, open source, royalty-free file format. AVIF has the potential to become the “next big thing” for sharing images in web content. It offers state-of-the-art features and performance, without the encumbrance of complicated licensing and patent royalties that have hampered comparable alternatives. It offers much better lossless compression compared to PNG or JPEG formats, with support for higher color depths and transparency. As support is not yet comprehensive, you should include fallbacks to formats with better browser support (i.e. using the <picture> element). Read more about the AVIF image format in the Image file type and format guide on MDN." 2021.10.08 https://hacks.mozilla.org/2021/10/lots-to-see-in-firefox-93/

>>fg-7N70N4MA minimum hardware support is an important factor, but it has more to do with the implementation written to handle the format, more than the format itself. If the major downside is speed, that is inconvenient, but not impossible to use. If all implementations require specific CPU features that older hardware do not have, that is a major issue. CPU use is also a concern for embedded platform, since they typically are less powerful and fan-less.

>>fg-H29PBHUQ >JXL will be a botnet format. Except it's not. The reference implementation of JXL is 3-clause BSD and the patent owner for all intents and purposes is Google, who grants a irrevocable license to do whatever the fuck you want. The patents are being held purely to prevent patent trolling. It's also being codified as an ISO/IEC standard.

I remember converting all My photos to jpeg 2000 to save space.