I saw some tests on it and it’s kind of a whatever feature. The iPhone depth of field is still far too deep even wide open. So the difference stopped down is kind of meaningless.
Most users will never use it, or I should say adjust the aperture, most people appear to be more interested in the video performance, and the video performance depends upon having very good software and hardware combined as one which is where Apple is able to outdo the competition, with Apple Silicon/video software, Apple appears to only care about still pictures up to a certain point, over the last five or six years. In short video is king in today’s YouTube age.
> Most users will never use it, or I should say adjust the aperture
This is like saying most users will never adjust the shutter speed. Of course they won't, because the software automatically adjusts it, just like it does on any traditional camera. For the aperture capable lens, the software adjusts the aperture automatically depending upon light and/or depth of field requirements of a scene.
And yes, photographs are still spectacularly important.
But...I don't get it regardless. You know that video also uses apertures on every such equipped device, right? Better depth of field if the environment allows it is a good thing.
> Apple appears to only care about still pictures up to a certain point
I feel like people are just saying silly bullshit now. Apple has made video a core part of their product reveals for years now. And current iPhones take outrageously good videos.
If a site creates some opaque token representing the request, and the token is signed by the ID service with no other information disclosure that "The user that presented this is of the appropriate age" that would seem like a reasonable compromise.
Token could be signed out-of-band to obscure the interaction between the parties.
“The audience of a changelog is entirely different than the audience for a commit log!
A changelog is user-facing”
I'd say that ship has probably sailed. Most companies are happy with “Bug Fixes & Performance Improvements”.
At least if they're not going to put the effort in, then a generated changelog is better than nothing.
The best thing that I'd used for auto-updated software with weekly updates was to prefix user-facing visible commits with "uv:" Then each week we search for them and either use the text as-is or massage it slightly. We even got it into the product itself in the Help/Release-notes menu.
Funny to ask to stop doing something I don't do or never even heard of. I typically only mark database schema migrations or other major things with special prefixes.
He confuses changelog with release notes. Doesnt know how to name commits and probably doesnt know how to name symbols either. Skill issue and he’s sad, now in public. Move on…
reply