srht is really designed for (and thus only really useful for) lone wolf developers who collaborate rarely, if ever, and with a very small number of collaborators who collaborate infrequently. It is not built for large teams with constant active collaboration, it falls down for this use case.
It’s hobby software for hobby users. (I don’t think this is a bad thing, but you should be aware of the product design goals of its author.)
This is wrong.
This is exactly the problematic attitude. I'm an OpenJDK author but not linux kernel contributor for mainly this reason. There are many people like me.
> majority of contributors to Linux, an extremely successful free software project, prefer the email-based workflow
This reminds me the many absurd conversations I had from my time in Goldman Sachs, few years ago. People with 15+ year tenures claiming Slang is the best answer to any- and everything. They just didn't know any better and stubbornly stuck to tooling and mindset straight out of 1995.
The internal cloud was just getting up to speed when I left, and that was more modern and also a joy to use.
There's a lot to dislike about working there, but in my experience, the firmwide tooling was excellent.
Windows and Office and AWS and GCP dwarf these foss projects.
There is a reason that Google, Amazon, Microsoft, and Apple don’t use email to collaborate on software.
You cannot possibly claim that the other side needs to cite their sources and then throw numbers like that out without any backing.
I say that as someone who don’t like GitHub, but overall it’s far from the worst tool an employer may impose to its employees.
Fake Edit: Oh this is HN. Never mind then.
I funnily think that many of the people poo-pooing the email patch method here, would just as merrily join in on HN were it an email mailing list collection, haha! :)
It is often used in GitHub CI workflows.