4 ms·

Sorry but if the error gives you the right command to run first time then it should just run it first time by default. Sane defaults for new users is good UX. N

Sorry but if the error gives you the right command to run first time then it should just run it first time by default. Sane defaults for new users is good UX. Not an error telling you exactly what command to run instead. It already knows what you intended, for Christ sakes, because it's telling you what you should copy and paste instead!

qlm 8y ago
It's not necessarily always the correct command to run, it's just suggesting what you probably want to do.
- jwdunne 8y ago
  Which should be the default, based on popular use. You can always use the command it suggests to do something different.
  - augbog 8y ago
    Well considering how many people who now know git and understand it, it doesn't make sense to do that necessarily. Rather they should make it a configurable option which do now see push.default (https://git-scm.com/docs/git-config https://git-scm.com/docs/git-config)
    - jwdunne 8y ago
      Right, which means changing it will harm the UX due to ingrained pattern. That's not what I'm arguing for. I'm arguing against the idea that showing an error message with the exact command to use is good UX - see the original comment. It is not.
zdragnar 8y ago
But it doesn't know what you intended. It's guessing. The consequences of guessing incorrectly could be very, very bad, as you are pushing your code to a remote host. Again, the whole point of git is that it is decentralized; there is no requirement that you have one single central server that you are pushing to; there could easily be multiple places that you might want to push something to. Using something as default that makes sense for a centralized VCS when git is not centralized is, imho, worse than bad UX, as it teaches incorrect assumptions. Again, this is table-stakes knowledge for using decentralized version control.

4 ms·

Sorry but if the error gives you the right command to run first time then it should just run it first time by default. Sane defaults for new users is good UX. N

by jwdunne 8y ago

qlm 8y ago
It's not necessarily always the correct command to run, it's just suggesting what you probably want to do.
- jwdunne 8y ago
  Which should be the default, based on popular use. You can always use the command it suggests to do something different.
  - augbog 8y ago
    Well considering how many people who now know git and understand it, it doesn't make sense to do that necessarily. Rather they should make it a configurable option which do now see push.default (https://git-scm.com/docs/git-config https://git-scm.com/docs/git-config)
    - jwdunne 8y ago
      Right, which means changing it will harm the UX due to ingrained pattern. That's not what I'm arguing for. I'm arguing against the idea that showing an error message with the exact command to use is good UX - see the original comment. It is not.
zdragnar 8y ago
But it doesn't know what you intended. It's guessing. The consequences of guessing incorrectly could be very, very bad, as you are pushing your code to a remote host. Again, the whole point of git is that it is decentralized; there is no requirement that you have one single central server that you are pushing to; there could easily be multiple places that you might want to push something to. Using something as default that makes sense for a centralized VCS when git is not centralized is, imho, worse than bad UX, as it teaches incorrect assumptions. Again, this is table-stakes knowledge for using decentralized version control.