3 ms·
Nobody is forcing anybody to make their code public. It's their choice. You can have your code on your machine and on your servers only. Hosting your code is an
by Walkman 11y ago
Nobody is forcing anybody to make their code public. It's their choice. You can have your code on your machine and on your servers only. Hosting your code is an option.
- pearjuice 11y agoAnd what if you are working with more than one person on the same private code base? You work on the same machine? Extreme programming?
- Walkman 11y agoYou probably don't know how easy it is to push your code to another machine through SSH and share a Git repository that way.
- pearjuice 11y agoActually I do, isn't that how it is most frequently done? Fact is that even though it works and you can set it up yourself, it is not a good solution to decentralizing a code base. You might have a private machine to which everybody ssh'es and pushes and pulls from, but only a few do that because they don't want to be/have the ops people who run that box. And that is including but not limited to issues and a sane UI for collaborations. That's very well the problem that github/bitbucket/gitlab and the like solve. So you are telling me that there is no problem and people should just use a private SSH connection to a box they own?
- sytse 11y agoFor many people hosting their code makes it easier to work on it, especially for collaboration, ci and deploys.