Earlier quoted context omitted.
I prefer getopt because it's more succinct and more standardized. I made sr.ht :) I can't give you an unbiased opinion, but naturally I think it's quite nice given that I designed it explicitly to suit my needs. Check out the marketing page for some more details: https://sourcehut.org
Heya, so I just checked out Sourcehut and despite really wanting to use it (and pay) I decided not to. But because I find the product cool, I figured I should note why. So, 1. My primary projects of which I need private hosting contain many (less than a GB, currently) "large" files hosted. Of course, these files need to be tied to the source code. Currently I'm solving this with Git LFS. Now, I'm not exactly tied to…
Regarding point 1, I do eventually want to add git lfs support.
Regarding point 2, the only thing I can say is "don't knock it until you've tried it". As someone who's spent thousands of hours each in GitHub, Gerrit, and email, as well as some time in GitLab, Gitea, and Phabricator, I've tried a lot of workflows and email is by far the most efficient. However, in the future I plan on adding web UIs for review and patch submission which are backed by email underneath, so you can use the web or email - whichever you prefer. I think you ought to give email an earnest shot, though.
Also, lots of people use a subset of SourceHut, like the CI service for example, while still hosting git repos on GitHub or GitLab. Because it's modular in design, each piece can be useful ala-carte or composed freely with other solutions.