this post was submitted on 06 Feb 2026
57 points (98.3% liked)
Programming
25416 readers
291 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 !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What, why?
Compared to e.g. pushing a button in VS code and having your browser pop up with a pre-filled in github PR page? It's clunky, but that doesn't mean it's not useful.
For starters it's entirely decentralised, a single email address is all you need to commit to anything, regardless of where and how it's hosted. There was actually an article on lobsters recently that I thought was quite neat, how the combination of a patch-based workflow and email allows for entirely offline development, something that's simply not possible with things like github or codeberg.
https://ploum.net/2026-01-31-offline-git-send-email.html
The fact that you can "send" an email without actually sending it means you can queue the patch submissions up offline and then send them whenever you're ready, along with downloading the replies.
Ah, the process you mean. patch itself is still useful.