Looks nice. Is there any reason to use getopt over flag in Go?
How do you find the experience with sr.ht?
How do you find the experience with sr.ht?
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:
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 the solution, I just want it to be fairly pain free and baked in, of which Git LFS does a good job on. I super look forward to Git LFS.
2. I know you're working on it, but I have no desire to change my workflow to be email oriented. I don't intend to debate it, it's just not what I desire. PR UIs would be hugely helpful.
#2 is barely an issue at all, because I know you're working on it. If I had GitLFS I would have signed up for $10/m as that's well worth it to me.
Appreciate the product, hope it does great things for you. I look forward to using it when/if you implement GitLFS or something like it :)
Thanks! As a potential customer I hope this was at least mildly helpful :)
edit: It should be noted that my GitLFS files are of course binary. 3D modeling, PSDs, that sort of thing.
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.
For now I'm building around Gitlab, possibly migrating to Github if I run out of LFS storage on Gitlab (Github lets you pay for more storage.. don't think I can on Gitlab yet..).
Appreciate your work :)
Its parser follows the POSIX utility syntax guidelines and behaves like most POSIX tools. The flag parser on the other hand is simpler, but can lead to some surprises if you are used to getopt-like parsing.