61–70 of 83 posts
Earlier quoted context omitted.
GitHub, GitLab, Gitea. Those all work fine. As long as you can easily tell the difference between them.
Agreed. Taco Bell, Del Taco, Taco Cabana, Taco Bueno, Del Taco, Fuzzy's Tacos... and it keeps going.
Good choice. It's memorable. I signed up as a paid user when it was last on hacker news. Got an email invoice. Then for the life of me could not remember what the service was called. Finally gave up trying to use it.
sourcehut on the other hand is one of too many source somethings. It's more prefessional for sure and if it is the official name we can still keep sir hat as a nickname I guess.
Mercurial support, fuck yeah: https://hg.sr.ht/ This is the killer feature for me. Why Mercurial? Here’s a list of Mercurial features that I think are really cool: Revsets – a domain-specific language for querying your commits Templates – a domain-specific language for altering the output of almost every command. Putting together these two you can do things like this: http://jordi.inversethought.com/blog/customising-…
It's also dying [1]. Git's the only version control system that's got legs [2]. [1] https://trends.google.com/trends/explore?date=all&q=%2Fm%2F0... [2] https://trends.google.com/trends/explore?date=all&q=%2Fm%2F0...
Or perhaps they're reflecting GitHub's dominance in the forge space and the fact that they only offer git, so a whole lot of people are more-or-less forced to learn something about git, so searches...
Or perhaps they're reflecting something about hg users preferring other search-engines than Google...
Drawing any sort of conclusive correlation between those Google search trends and actual usage or desire to use one or other distributed VCS is a fool's game.
As of posting, the info on this site is very lean, but going forward sourcehut seems to be the name for the software suite of the service 'sr.ht'. The linkage is implied by the quote on the site that " sr.ht is a hosted instance of sourcehut provided for your convenience ". The impetus behind the branding clarification seems to be this HN thread [1]. For more history, see the the debut announcement [2] and its corres…
Definitely glad that he changed it. I was concerned about that holding his growth back when he did the Show on Lobsters. Also, some people can't access sites with weird domains due to corporate firewalls. A .org might prevent that. Looking back at the thread, it looks like the new name was suggested back then by neuromanc: https://lobste.rs/s/cqangw/sr_ht_hacker_s_forge_now_open_for... I like how the proposed name fi…
Funny to see it came from reddit, thanks.
"All features work without JavaScript" oh hello there, my new friend. :)
As the owner of e.ht, welcome to the world of obscure short TLD’s!
As of posting, the info on this site is very lean, but going forward sourcehut seems to be the name for the software suite of the service 'sr.ht'. The linkage is implied by the quote on the site that " sr.ht is a hosted instance of sourcehut provided for your convenience ". The impetus behind the branding clarification seems to be this HN thread [1]. For more history, see the the debut announcement [2] and its corres…
I think this is a bad move. There is already: SourceTree SourceView SourceForge TheSource SourceCode SourceDaddy OutSource By adding more "Source", you are just diluting value of source brand. It will be interesting to see how many more "Source" untill we stop using Source at all? Same is the thing with "Git" and Docker escaped this issue by prohibiting use of "Docker" in non docker owned companies.
"Source" is not the brand, it's the literal description of what most (all?) of these products and services deal with.
The prefixes/suffixes make the brand. Having a very relatable/descriptive term like "Source" in that brand adds clarity.
Mercurial support, fuck yeah: https://hg.sr.ht/ This is the killer feature for me. Why Mercurial? Here’s a list of Mercurial features that I think are really cool: Revsets – a domain-specific language for querying your commits Templates – a domain-specific language for altering the output of almost every command. Putting together these two you can do things like this: http://jordi.inversethought.com/blog/customising-…
Git UI is just terrible. I am sad that Microsoft chose git for VFS and not mercurial. Mercurial would have worked great for their windows mono-repo
Mercurial support, fuck yeah: https://hg.sr.ht/ This is the killer feature for me. Why Mercurial? Here’s a list of Mercurial features that I think are really cool: Revsets – a domain-specific language for querying your commits Templates – a domain-specific language for altering the output of almost every command. Putting together these two you can do things like this: http://jordi.inversethought.com/blog/customising-…
It's also dying [1]. Git's the only version control system that's got legs [2]. [1] https://trends.google.com/trends/explore?date=all&q=%2Fm%2F0... [2] https://trends.google.com/trends/explore?date=all&q=%2Fm%2F0...
Projects like pijul interest me, since they work in a fundamentally different way. Pijul is a "nicer" version of darcs. Git killed darcs not by being nicer but by being faster, and pijul is also faster than darcs, so maybe there's hope ;)
(Of course, most of git's momentum came from huge projects using it, like Linux and Xorg; yet being huge is precisely what forced those projects to favour speed at the cost of "niceness". If a "nice" system existed that was fast enough to handle Linux, Torvalds would probably never have written git).