3 ms·
GitHub must certainly does not have a monopoly on the social aspects of version control. But it does seem, from recent experience with e.g. Mastodon that the re
by jeffrallen 1y ago
GitHub must certainly does not have a monopoly on the social aspects of version control. But it does seem, from recent experience with e.g. Mastodon that the revealed preferences of users of social apps is for centralization. Even users (software developers) who likely have a higher familiarity with the pros and cons of centralization.
Also: Ask yourself why did Linus "solve" VC decentralization, but not social software decentralization. Probably because one is "easy" and the other is "not obviously possible". :)
- overfeed 1y ago> Ask yourself why did Linus "solve" VC decentralization, but not social software decentralization Perhaps because it was out of scope? Linux kernel diffs are emailed, so Linus solved for email as the social layer, and it works well with mailing lists. If Pull Requests had predated git and the kernel had used them, Linus would have solved for