WebP lossless is close to state of the art and widely available. It's also not widely used. The takeaway seems to be that absolute best performance for lossless compression isn't that important, or at least it won't get you widely adopted.
I don't know that i have ever used jpg or png lossless in practical usage (e.g. I don't think 99.9% of mobile app or web usecases are for lossless). WebP lossy performance is just not worth it in practice, which is why WebP never took off IMO.
Are there usecases for lossless other than archival?
I definitely noticed when the Play Store switched to lossy icons. I can still notice it to this day, though they did at least make it harder to notice (it was especially apparent on low-DPI displays). Fortunately, the apps once installed still seem to use lossless icons.
A lot of images should be lossless. Icons/pictograms/emoji, diagrams and line drawings (when rasterized), screenshots, etc. You can sometimes get away with large-resolution lossy for some of these if you scale it down, but that doesn't necessarily translate into a smaller file size than a lossless image at the intended resolution.
There's another problem with lossy images, which is re-encoding. Any app/site that lets you upload/share an image but also insists on re-encoding it can quickly turn it into pixelated mush.
Only downside is that webp lossless requires RGB colorspace so you can't, for example, save direct YUV frames from a video losslessly. AVIF lossless does support this though.
That's a critique of `async`, not of `using` though, right? This doesn't seem to make functions more colored than they already are as far as I understand.
In my experience they're not great with mathy code for example. I had a function that did subdivision of certain splines and had some of the coefficients wrong. I pasted my function into these reasoning models and asked "does this look right?" and they all had a whole bunch of math formulas in their reasoning and said "this is correct" (which it wasn't).
Actually, almost everything changes slightly - the number, shape and pattern of the chairs, the number and pattern of the pillows, the pattern of the curtains, the scene outside the window, the wooden part of the table, the pattern of the carpet... The blue couch stays largely the same, it just loses some detail...
Yes, first a still life and something impressionist, then a blob and a blob, then a smear and a smear. And what about the reflections and transparency of the glass table top? It gets very indistinct. Keep working at the same image and it looks like you'll end up with some Deep Dream weirdness.
I think the fireplace might be turning into some tiny stairs leading down. :)
Blue bubbles don't mean privacy, and green bubbles don't mean insecure. I would presume encrypted RCS would satisfy privacy, and would remain green to indicate it doesn't support iMessage-specific features.
iMessage is encrypted. Blue means the “SMS” was sent over iMessage and it is secure. Green means it was sent as a normal SMS. This is super helpful for non-technical people that want privacy.
Blue means iMessage, and supports iMessage features.
Green means not-iMessage and supports SMS / MMS / RCS features.
Presumably when Apple rolls this out, both blue and green messages could be end-to-end encrypted. It remains to be seen whether Apple will add an indicator for RCS (and potentially iMessage) encrypted messages. I could imagine them being jerks about it and not indicating when green messages are just as secure as iMessage, or they adjust their messages that iMessage is more secure/private because Apple trusts their own key exchange more than RCS.
