this post was submitted on 20 Jul 2023
393 points (95.6% liked)
Programming
17398 readers
215 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is only true for the merge request workflow and not at all a problem for the patch workflow, which can work entirely via email (and is in my eyes simpler). Have a look at https://git-send-email.io/ if you want to learn about it. This is the true decentralized spirit of git. :)
@unicorn
> Have a look at git-send-email.io if you want to learn about it.
But I don't. And that is exactly the barrier I'm talking about.
By this logic, you want a complete monopoly of a single platform? Because that's the only possible way to have "no barrier". Unless GitHub starts federating with some kind of standardized protocol. This is a huge technological and monetary barrier for GitHub, which is why it will never happen on its own, so if users are not willing to try platform-independent workflows then the problem is frankly not the competing platforms.