AVIF and webp kind of only exist for the web, they get used when you want to really crunch down on data as much as possible. They aren’t really used for files you’d save on your computer or get out of a camera.
JPEG XL is replacing regular jpeg and heif for photography. It offers 16 bit color rather than 8 from jpeg and HDR support along with a ton of extra features.
Every OS but Android supports it, safari supports it, chrome and Firefox have it behind a beta flag.
> AVIF and webp kind of only exist for the web, they get used when you want to really crunch down on data as much as possible.
Speaking only for webp here. It is designed to balance download and decompression time to load faster than it's competitors. Compressed filesize isn't generally smaller and compression time is notoriously slow.
It's an open standard because the concepts and reference implementation are free and open source even if the PDF is paywalled. Realistically you could just pirate the PDF and write a jpeg xl encoder/decoder and your code wouldn't be infringing on any patents.
Splitting hairs on terminology I guess. Very few people are interested in the PDF that specifies the format vs being able to include decoders in software and on devices without paying a royalty for every device. There are alternative documents and the last draft copy which are free legally. As well as the reference code.
Before the world of internet, Open does not always mean free. They are two different concept. A proprietary codec isn't open, and you can't use it everywhere unless the owner allows you to or provided tools and support. Microsoft with their WMV and Realmedia with RVMB for example. H.263 and H.264 was called an open standard at the time, any body can buy and implement it.
They added it back as an experimental flag again. Likely the new rust based decoder and adoption in to other platforms and standards changed their decision.
jpeg xl is also now used for the latest version of the DNG raw image format, and the iphone now encodes raw images as jpeg xl in DNG. It's so clearly the future for photography that Google is holding back. Apple surprisingly has been the first with full support everywhere in their OSs and in Safari.
I just wanted to add the decision for JXL inside DNG was well known even before it happened and Chrome still said no. Adobe and Intel along with plenty of other players in the industry screams this is so good they are all adding support. But still Google said no.
And to make matter worst the publish the worst comparison document and benchmarks for AVIF against JXL.
Huge fan of JXL, but this article feels pretty AI sloppy. Not much said here, coming from the google blog I was hoping for some news about how they are pushing the format forward by introducing decoders in to Android and enabling on Chrome.
Android is the only mainstream OS that does not support JPEG XL right now.
I initially read the articles without images (they don't load for an unrelated reason) and actually felt it gave a good summary of JPEGXL underlying technologies and history, I also learned some new stuff.
I think the images might give a slop framing which is undue
Probably got some time to go. The new rust decoder likely needs more time to be proven reliable and safe, and Firefox doesn't even get the flag to turn it on until the next release 152.
The massive PRs is something that probably has to end. You can ai generate smaller changes in reviewable PR sizes. It probably even helps the AI code review tools to break the work in to smaller logical chunks too.
It's also IMAP is an awful protocol with so many glaring issues its impossible for a modern client to paper over them. Fastmail invented JMAP but it doesn't seem to have taken off with any other providers.
From memory, there are no bulk actions, so if you want to say select all emails and delete you have to send thousands of requests. If you want to rename a folder you have to send a request for every email in the folder. There is no way to set up filters that run server side, there is no way to get push notifications.
And probably a million other things that don’t hold up today.
Sending those thousands of requests is something your mail client does for you. Deleting 5000 emails takes a few minutes, but how often do you do that? I can select a bunch of emails in Thunderbird and just do stuff with it just fine.
For server side filters I just set them up in Fastmail using the web UI. That's the type of action I do once or twice a year, so totally OK to hop on over to the web app for just that.
I have no idea what you mean by 'push notifications'. I have Thunderbird open on my desktop, and it shows me when there is email. I have K9 on my smartphone, and it shows me when there is email (I don't have it set up to display notifications, but that seems possible). That's basically all I need to do email.
An intuitive way to understand it is imagining that there was a system where if you stole something, you 100% of the time got hit with a charge to your account of the item value + $10. No one would steal again even if the penalty for getting caught was relatively nothing. Because the feedback loop is so short and guaranteed.
No ones life would be ruined over a dumb choice and yet they would change their behavior very fast.
It’s still the same. If you steal something and have no money you lose the item and get some small penalty, perhaps a day in jail. If there is absolutely no chance you’d get away with it, everyone quickly realises there is no point.
JPEG XL is replacing regular jpeg and heif for photography. It offers 16 bit color rather than 8 from jpeg and HDR support along with a ton of extra features.
Every OS but Android supports it, safari supports it, chrome and Firefox have it behind a beta flag.
reply