Everyone comes to the plate with different experiences/expectations. You can't hope to satisfy everyone.
hg branch new-feature
If you want it to branch from a different changeset than the one you're on, then: hg update deadbeef
hg branch new-feature
No flags, no orgin/newfeature (what does that even mean?), just the commands describing exactly what you're doing.git checkout -b new-feature
The only diff is -b, which is fine to me because it makes it clear that you are doing two things. You don't need the origin/newfeature stuff for the common case. I'm assuming this is what 'hg branch new-feature' is doing. How do you create a branch and not switch to it?
hg branch new-feature
hg update default
But why would you not want to switch to a branch you just created? Why create the branch if you're not going to work on it?'hg branch foo' just marks the working directory as branch foo. The 'hg update default' would then update back to the default branch and mark the working directory as being on 'default'.
To really just create a new branch you do: 'hg branch foo; hg commit -m "Create a new branch."' Two steps, but like you said, it's probably not something you'd be doing very often anyway.