ranson

I've been very critical of Apple's anti-steering approach and stance against a user's right to install whatever they want on their device without being gatekept by Apple.

But I do not see any issue with the "scare screen" here. It does not add any extra steps that make the process of installing the app more difficult, and nothing about the messaging is untrue. So It should be well within Apple's right to disclose this information before the user downloads the app.

ensoniq said:

No one at AppleInsider or MacRumors or 9to5Mac gets crapped on when they make mistakes.  Why hold Prosser to a different standard?

Because their accuracy is notably better? Because they don't drag out their big "reveals" on twitter with multi-day countdowns to maximize revenue? Or do silly stunts like shaving eyebrows? Or sensationalize and hype up everything as if it's the most incredible scoop ever made?

And don't get me wrong, I have leveled blunt criticisms at all three of these sites you mentioned on their comments sections. But at least their authors appear to be focused more on sharing the information than they are about bringing attention to themselves.

Jon doesn't have any intel. This is his attempt to climb back up to the high dive platform after a few years of flops and busts from his previous fake scoops.

If anyone plans to use this, I have one recommendation, which is to "git init" your project and commit your own changes before letting an AI edit your code. Do this even if you just plan to work on the project locally and are not planning to push it up to github or some other remote location. The reason is because, just like collaborative coding with another human, it is important to know what was changed and when. Doing this will allow you to see (via VS Code's built-in git diff feature) exactly what lines were changed, and easily discard those changes in the event that GPT has introduced a defect or other undesirable outcome in your code.

SuntanIronMan said:

MagSafe isn’t just an array of magnets though. It’s a technical specification for wireless charging. Adding magnets to a case doesn’t make a phone MagSafe. It’s compatible with MagSafe, but the phone is still Qi(1) that is limited to 7.5w — while the MagSafe of the iPhone 16 (no-suffix/Plus/Pro/Pro Max) can go up to 25w. The difference between 25w and 7.5w is quite significant. I know not everybody cares about wireless charging (and that’s perfectly fine), but… 25w vs 7.5w is a notable difference.

That's why I said Spigen offers "magnetic charging cases".  I know it is not MagSafe, and that Apple is not going to give the nice swirly animation or the maximum charging output.  I quoted William complaining about the loss of convenience of just popping it on the stand, and pointed out that this capability is not gone when paired with any magnetic charging case. Most people who use MagSafe with a stand charge their phone overnight while the phone is in Nightstand mode. They don't care how fast it charges overnight. People know the fastest way to charge a phone is to plug it in and that true MagSafe is slower, while non-MagSafe induction charging is slowest.