6 ms·

I use github a lot but I'm not too worried about the vendor lock-in. Since git is by nature distributed it's trivial to migrate the code elsewhere. The real pro

by simias 8y ago

I use github a lot but I'm not too worried about the vendor lock-in. Since git is by nature distributed it's trivial to migrate the code elsewhere. The real problem is migrating the issues (but there are solutions for that as well, even if it's a bit more clunky) and the "social network" aspect but I don't care much for that myself. But you're right, maybe IPFS plus something like Fossil (including issues in the VCS directly) could be a good solution to have a truly decentralized "platform".

matt_the_bass 8y ago
For me and my team, git is not the tie-in for github. PRs are. Those are the proprietary parts of GitHubs value proposition. We use them all the time and fine the review process pretty convenient. I haven’t tried gitlabs equivalent. I’m sure we could use them but we’d need to adjust our workflow. So we’ll stay at github until the cost of migrating is less than any pain points we find at GitHub
- tkxxx7 8y ago
  PRs seem to have the same functionality everywhere; I haven’t seen anything in Github that I couldn’t do in Bitbucket or Gitlab.
  - dsumenkovic 8y ago
    PRs are related to MRs (Merge Requests), howver MRs have some additional features. Here you can read more about it https://about.gitlab.com/comparison/gitlab-merge-request-vs-github-pull-request.html https://about.gitlab.com/comparison/gitlab-merge-request-vs-...
- deleted 8y ago
  [deleted]
bhrgunatha 8y ago
What about user lock-out?
- xte 8y ago
  I do not know if it's a joke for you but it's a discussion point: my point is that devs are not "mass users" so they MUST know the tools of the trade. So if I agree for instance that LaTeX for the classic stereotypical secretary it's a lock-out software despite it's excellent characteristics, I can't accept the same argument for an IT professional and even for a casual hobbyist programmer.
  - pjmlp 8y ago
    I had the pleasure of writing my graduation thesis and a couple of university assignments reports in LaTeX. I don't miss it at all.

by simias 8y ago

matt_the_bass 8y ago

For me and my team, git is not the tie-in for github. PRs are. Those are the proprietary parts of GitHubs value proposition. We use them all the time and fine the review process pretty convenient. I haven’t tried gitlabs equivalent. I’m sure we could use them but we’d need to adjust our workflow. So we’ll stay at github until the cost of migrating is less than any pain points we find at GitHub

tkxxx7 8y ago
PRs seem to have the same functionality everywhere; I haven’t seen anything in Github that I couldn’t do in Bitbucket or Gitlab.
- dsumenkovic 8y ago
  PRs are related to MRs (Merge Requests), howver MRs have some additional features. Here you can read more about it https://about.gitlab.com/comparison/gitlab-merge-request-vs-github-pull-request.html https://about.gitlab.com/comparison/gitlab-merge-request-vs-...
deleted 8y ago
[deleted]

bhrgunatha 8y ago

What about user lock-out?

xte 8y ago
I do not know if it's a joke for you but it's a discussion point: my point is that devs are not "mass users" so they MUST know the tools of the trade. So if I agree for instance that LaTeX for the classic stereotypical secretary it's a lock-out software despite it's excellent characteristics, I can't accept the same argument for an IT professional and even for a casual hobbyist programmer.
- pjmlp 8y ago
  I had the pleasure of writing my graduation thesis and a couple of university assignments reports in LaTeX. I don't miss it at all.