As I replied in else where here, I do not run any Apple Services on my Mac hardware. I do on my iDevices though, but that's a different topic. Again, I could be the edge case
But if you're being pedantic, I meant Apple SaaS requiring monthly payments or any other form of using something from Apple where I give them money outside the purchase of their hardware.
If you're talking background services as part of macOS, then you're being intentionally obtuse to the point and you know it
Literally no piece of software is bug-free. Not one. What are you talking about? Of course it’s impossible to test all inputs, because there’s going to be inputs that you can’t even convince of at the time of designing. What if your application suddenly runs at 1000000x the intended speed because hardware improves so much? How do you test for that?
Yes it does. It ages. But even if it doesn't, my point still stands. Or are you insinuating that the engineers over at Intel, AMD and Apple don't know what they're doing, because clearly their CPUs aren't flawless and still have bugs, like Spectre/Meltdown.
It deteriorates, it doesn't change. The functionality is still there and no modern hardware deteriorates to a failing state before it gets obsolete. Yes, I am insinuating that the engineers at intel, AMD, apple and nvidia are incentivized to prioritize expedient solutions over developing more robust architectures, as evidenced by vulnerabilities like Spectre and Meltdown.
I don’t think it’s that easy. I’m sure Intel, AMD and Apple have a very sophisticated suite of “known working systems” that they use to test their new chips, and they still build in bugs that security researchers find 5 years later. It’s impossible to test and verify such complex designs fully.
There’s a difference between not knowing multiplication and just refusing any logical thinking at all. We already see this a lot in adults today. Many are just too lazy to turn on their brain, because it’s easier to call, ask on Reddit or whatever, even if it takes ten times longer than just doing the thinking yourself.
This is just the perfection of that. And it’s suuuuper scary, because it trains you to be a brain dead monkey that literally believes anything ChatGPT tells you. And we know how that’ll work out.
Well it’s obviously not hilarious in a „haha funny“ kind of way. It’s hilarious in a „I can’t believe this is real life“ kind of way. It’s a headline you’d expect to read on The Onion.
And I blame the EU for not making this the law. Just force everyone to adhere to the setting and be done with it. But no, instead we got this bullshit.
It’s not necessarily hard. But it’s cumbersome and just one of the worst codebases I ever had the pleasure of working with. Basically everything about it is legacy, bad design choices, hacks, workarounds and compatibility fixes. That’s what makes it complex. It needs a rewrite 10 years ago. But due to the deep integration of thousands of plugins that will never be possible.
It’s hard to put it into solid feedback and examples, because it is highly subjective. But I also find the image results from Kagi lacking, while I really enjoy the text based results. Especially for more specific queries, the image search just doesn’t hold up.
I just tried generating an example. Take the query “screenshot nero burning rom windows xp” - of the first 10 images, only 6 are screenshots of the program on Kagi. On Google, it’s a solid 10/10.
Of course it’s hard to take just one example, but it reflects the general feeling I have when using the image search quite well. The results aren’t necessarily terrible, it’s just that they aren’t as relevant as Google’s.
All right, mister smarty pants. Let's hear it then: What is a better explanation than "this app need camera permissions, because it takes photos, because it is a fucking camera app"?
Halide is a professional-grade camera application that offers advanced photography features such as manual controls, RAW and ProRAW capture, live histograms, focus peaking, depth capture, macro photography, augmented reality overlays, adaptive gesture controls, exposure tools like zebra stripes, and advanced video recording options. In order to provide these functionalities, these require camera permissions to access and control the device's camera hardware in real-time. Each feature relies on direct interaction with the camera to adjust settings, analyze live image data, and offer immediate feedback, making camera access essential for the app to function as intended and enhance the overall user experience.
moral of the story. spend 3 extra minutes writing something out and save yourself from a headache.
why are we assuming every person that reviews apps knows what ur app does? with submissions like this the explain it like im 5 approach is necessary.
I agree that permission requests should include sufficient context -- but I think that paragraph is way too long for the purpose. People do not read unexpected dialog text. I'd save that for the App Store description, when people are more receptive to detail.
For the permission request, I'd condense your paragraph into a sentence or two.
It's not unusual to download an app, but not launch it immediately. Demanding that the user remember your App Store description is unfair. It's your baby, not theirs.
They might not launch your app for hours or days after downloading. And Apple, reasonably I think, wants developers to try harder to accommodate user's realities.
