Ben Finney <ben+deb...@benfinney.id.au> writes: > We're told that GitHub has a raft of features that make it superior, > until it's pointed out that those features are GitHub-specific and > incompatible with collaborators from outside; then, conveniently, the > specialness of those features dwindles to insignificance because we can > access the repo's commits.
It's a UI. The UI is really nice. That's why people use it. But lock-in implies more than a really nice UI that people use because it's superior. Lock-in implies something you're trapped into using even when it's *inferior*, and that's what people are taking issue with. For better or for ill, people use GitHub because it's *a really good product*, not because of some sort of nefarious lock-in strategy that holds people's data captive. The data that's to some extent captive in GitHub (like issues) are not really a strong point for GitHub. There are a lot of better issue trackers out there. (Like *cough* Atlassian, which is a much different conversation.) The repositories and Git management are the very nice features of GitHub, and there's nothing there data-wise you can't pretty trivially extract. It's just a very nice UI. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87lhhot4ey....@hope.eyrie.org
