And today it is Apple, and I'm curious to see whether HN folks feel the similar passion. Historically, people pick up pitch forks for Google but give Apple a pass - so looking forward to the conversation here.
Nevertheless, this serves as an excellent demonstration of the problem with the changes Google are making, since they would allow Google to do exactly what Apple just did.
- It isn't really a "new format". It's an update to the existing format. - It is very backwards compatible. -- Old programs will load new PNGs to the best of their capability. A user will still know "that is a picture of a red apple".
There also seems to be some confusion about how PNGs work internally. Short and sweet: - There are chunks of data. -- Chunks have a name, which says what data it contains. A program can skip a chunk it doesn't recognize. - There is only one image stream.
What sort of improvements might we expect? Is there a chance of it rivalling lossless WebP and JPEG XL?
Me too. There are still German companies where coworkers address others with Herr or Frau followed by their last name.
I find it also interesting how people that learn German understand the difference between the "you" in formal ("sie") and informal ("du") version, but often don't understand in which context du use them. In most cases you can use the informal "du" nowadays, especially when you are out with somebody for a beer.
After elementary school we had this interesting shift form addressing the other children with first name to addressing them with last name. We were circa 11 years old.
We also pretty much always use first name, at least everywhere I've been. Would feel weird to call people by their last name.
> You’re not affected if (and only if) . . . > You browse on desktop computers or use iOS (iPhones)
At the very least they should step back and allow companies to enforce safeguards because they clearly lack the understanding or foresight to do so effectively.
The simple way for the EU to beat Meta is to stop being so cheap: break the WhatsApp dependency by actually paying properly for something that has a decent UX and doesn't track you. If you aren't willing to do this you will be exploited over and over again. TANSTAAFL
On https://localmess.github.io/, they think that this is technically possible on iOS too, and the main reason it wasn't done there is due to restrictions on apps running in the background.
This is nothing new that has been opened up because of those regulations.
Pop songs for example, are heavily compressed because "compressed" music sounds "better" on cheap external speakers with bad dynamic range. Kinda like increasing the saturation on a cheap TFT panel.
On both Android & iOS/MacOS it's not that HDR is ignoring your screen brightness, but rather the brightness slider is controlling the SDR range and then yes HDR can exceed that, that's the singular purpose of HDR to be honest. All the other purported benefits of HDR are at best just about HDR video profiles and at worst just nonsense bullshit. The only thing HDR actually does is allow for brighter colors vs. SDR. When used selectively this really enhances a scene. But restraint is hard, and most forms of HDR content production are shit. The HDR images that newer iPhones and Pixel phones are capturing are generally quite good because they are actually restrained, but then ironically both of them have horrible HDR video that's just obnoxiously bright.
It's not just the HDR content that gets brighter, but SDR content too. When I test it in Chrome on Android, if an HDR image shows up on screen the phone start overriding the brightness slider completely and making everything brighter, including the phone's system UI.
>The only thing HDR actually does is allow for brighter colors vs. SDR.
Not just brighter, but also darker, so it can preserve detail in dark areas rather than crushing them.