I'm pretty sure more people would read it to the end if it didn't seem like AI output, yes.. At the very least you would have fewer (maybe not 0!) comments here saying it's AI slop.
I think the point people are making is that when the text has an "AI smell" (it does), we immediately lose trust in the veracity of any claim being made and feel like continuing to read what is possibly a hallucinated fiction is a complete waste of time.
At this point we're all used to skimming through thousands of AI-generated sentences every working day and constantly thinking "this is likely to be 20% bullshit", it's hard to turn that off even if I try.
They didn't say "nobody can replace the battery themselves", and "you" here was probably intended to mean "a normal consumer". Relative to items with replaceable batteries (a TV remote control, a camera, a pre-iPhone mobile phone), the batteries are extremely hard to replace.
The batteries are also not safe to replace, relative to items with replaceable batteries. There is a very low chance of me accidentally damaging my TV remote control while replacing the batteries.
None of the information you're responding to is false, and it's perhaps worth asking yourself why you're here defending Apple.
There's an easier argument that is simply "But Samsung!".
That was a Windows laptop, local SSD, about 200gb of raw files (fuji, pentax) from this year so far. Plenty of ram, plenty of spare storage, but no discrete GPU which might have been the issue. I might try it on Linux at some point.
I thought the same when I got a Fuji, but the issue is support for the X-Trans sensor. Turns out that converting to DNG doesn't change that and software that opens the DNG still needs to understand how to use the data in it.
I'm a naturally paranoid, very detail-oriented, man who has been a professional software developer for >25 years. Do you know anyone who read the full terms and conditions for their last car rental agreement prior to signing anything? I did that.
I do not expect other people to be as careful with this stuff as I am, and my perception of risk comes not only from the "hang on, wtf?" feeling when reading official docs but also from seeing what supposedly technical users are talking about actually doing on Reddit, here, etc.
Of course I use Claude Code, I'm not a Luddite (though they had a point), but I don't trust it and I don't think other people should either.
The companies selling us the service aren't saying "you should treat this LLM as a potentially hostile user on your machine and set up a new restricted account for it accordingly", they're just saying "download our app! connect it to all your stuff!" and we can't really blame ordinary users for doing that and getting into trouble.
Sure, there's "deliberate practice" and it matters - but so many people seem to think if they're playing that's what they should be doing, or it's a waste of time. In reality that often isn't much fun, and they start to associate the instrument with this sort of difficult and often disappointing experience, and they give up.
I'm only good enough to impress people who don't know what a good guitar player sounds like.
My advice to people, which seems to work OK, is just to have the guitar out and ready to play wherever you're likely to be - maybe even in the way so it has to be moved sometimes - and just pick it up and play it as often as possible.
Waiting for the kettle to boil? Play the guitar. TV is showing ads? Mute it and play the guitar. Your partner needs to go to the bathroom before you both go out? Play the guitar.
It doesn't matter what you play, it doesn't have to be good, it can be a random improvisation, it can be scales. Your fingers are learning.
For me it was the "it's not x"/"it's y" stuff and some other structures Claude is very fond of using all the time. Perhaps humans are starting to write like LLMs!
Obviously if you're running Claude Code you need a token for that and an internet connection, that's kind of a given. What I'm talking about is permission (OS level, not a leaky sandbox) to access the user's files, environment variables, project credentials for git remotes, signing keys, etc etc.
The user thing is what I currently do too. I've thought about containers but then it's confusing for everyone when I ask it to create and use containers itself.
So don't let them interact with anything external. You can push and pull to their git project folders over the local filesystem or network, they don't even need access to a remote.