The argument is that a beginner might not notice a command falls. The && prevents further execution.
Personally I’ve seen that happen several times myself. Beginners are just not used to reading the cmd outputs and I can’t blame them. There are many CLI tools with awful error reporting out there.
That’s why showing the expected outcome is also very important. It can feel very verbose, but the number of times I’ve been unclear as to if something worked because the documentation goes on immediately to the next step without demonstrating the success/failure states is extremely frustrating.
If it’s a beginner trying to learn those commands, definitely the latter.
If it’s a beginner trying to set up their environment for the actual thing they’re trying to learn, then a fire and forget single command is more user-friendly.
I don’t quite agree that for a beginer being presented with
is better than
All those symbols and “–yes” used to feel quite cryptic to me.
The argument is that a beginner might not notice a command falls. The && prevents further execution.
Personally I’ve seen that happen several times myself. Beginners are just not used to reading the cmd outputs and I can’t blame them. There are many CLI tools with awful error reporting out there.
That’s why showing the expected outcome is also very important. It can feel very verbose, but the number of times I’ve been unclear as to if something worked because the documentation goes on immediately to the next step without demonstrating the success/failure states is extremely frustrating.
yeah, I’d give it as 4 separate copy-pastable commands and then write “or as one command…”
It’s not the same, though. One will stop if a previous command fails, the other will continue.
If it’s a beginner trying to learn those commands, definitely the latter.
If it’s a beginner trying to set up their environment for the actual thing they’re trying to learn, then a fire and forget single command is more user-friendly.
deleted by creator