Comment by indigochill
8 years ago
Heck, I already prefer Gitlab and/or Bitbucket because they let me run free (or at least self-hosted in Gitlab's case, not sure what their hosted option's like) private repos. Github's just got the mindshare going for it. But maybe now that'll change.
Gitlab also lets you register private gitlab-runners on gitlab.com, which is a killer feature for running CI on setups that aren't plain docker-in-the-cloud (such as integration-testing apps that require resources on our LAN, or macOS/iOS builds with private keychain items that is much easier to configure on a local Mac). (A side bonus is that you don't even have to pay for any CI "minutes")
If you ever get something for free, remember something somewhere is subsidizing it. Whether that's the other paid accounts, which therefore must be uncompetitively priced, VC funding (which will eventually run out), or your data is sold.
I can't speak for Gitlab, but offering free Bitbucket should easily pay for itself as introduction to the Atlassian ecosystem.
Our experience went like this: We got Bitbucket for out project for the good free private repos (and a few other reasons). When it came to choosing a ticket system, being on Bitbucket made choosing Jira a no-brainer (one of the best ticket systems, good integration with Bitbucket, familiar interface). Then we needed a better wiki for internal documentation, so we naturally went with Confluence.
So getting free Bitbucket heavily influenced our decision to buy two other products from the same company, and we are about to buy into their CI system (Bitbucket Pipelines, not the other one). We don't regret any of those choices, but they might have looked different if we were on Github.
> your data is sold
It's now easier to see some of this, with the GDPR rules.
The Gitlab cookie page lists 80 "marketing" cookies which may be set: https://about.gitlab.com/privacy/cookies/
Wow. On the one hand I'm impressed with the openness (almost - what does purpose='unclassified' mean?), as well as the option to elect which cookie category I agree to. On the other hand... my, that's a lot of tracking!
1 reply →
Most of which you can now disable disallow on first visit.
I use a huge amount of open-source software which I do not believe is subsidized.
Some is, eg some linux/gnome devs are paid to contribute. But many smaller projects/components are volunteer-only.
> But many smaller projects/components are volunteer-only.
Someone is paying for it with their spare time. Spare time doesn't last forever.
If you're not paying for something, you should see it either as a temporary shortcut that eventually needs a more sustainable fix, or something you don't care about if it disappears.
1 reply →
It's subsidized by those volunteers' time. Time that could otherwise be spent on other things.
Granted, there's nothing nefarious about this, but there isn't anything necessarily nefarious about the fact that anything you get for free is being paid for somewhere else. Just potentially nefarious, if you don't know what's paying for it.
...the other paid accounts, which therefore must be uncompetitively priced,...
That doesn't follow. If the paid accounts are selling, then they must be priced appropriately relative to their competition and the value they provide. The cost doesn't factor into it - and free accounts are just a marketing cost, like putting up a billboard.
A public and a private repo costs the same to host, so I don’t see your point
I'd say +1 for GitLab. I just checked it out and like the UI better than GitHub anyways. I'm switching over and not looking back.
That's one big reason why we switched.
The other was the self hosted option.
I switched jobs and went from Github to Bitbucket about 6 months ago. I've found bitbucket to be consistently and noticeably slower than github both in its web UI and in pushes/pulls, with more downtime. You pay for those private repos one way or another.
I too felt this pain. UI feels "heavy" in comparison to Github.
There are obvious, simple updates that could be made to the UI to fix significant pain points. This one [1] brought me much pain every time I installed a new package via yarn.
1 - https://bitbucket.org/site/master/issues/7086/add-the-abilit...
> Github's just got the mindshare going for it.
But in more ways than just the users. If you want tu use most of the popular integrations, the often github-only. Things like TravisCI are suddenly what makes me open a new project on GH rather than GL.
I'm sure GitHub will introduce free private repos soon enough.
I'd be surprised if the announcement didn't also come with that change. Easiest way to even the field.
If Microsoft decides to make GitHub free for all, this can honestly have a devastating affect on GitLab and Bitbucket. I really think Microsoft is a lot more interested in:
- capturing developer data for ML/AI research
- identify new product ideas
- identify ways to improve existing products
- create a funnel to existing products
Especially since Microsoft's own version control thing has this.
Well, sort of. It's limited to 5 contributors, which is kind of a big deal if you're on a serious team.
1 reply →
They do have free private repos for academic researchers already.
What makes you think the same thing won’t happen to GitLab?
No one would’ve dreamed of this happening 5-10 years back.
I expect it'll happen to Gitlab at some point, but the beauty of self-hosted is that I can cut ties with the organization and continue using their software anyway because it's entirely running on my machine.
Which, incidentally, is just one reason I usually strongly prefer self-hosted options over SaaS. You're not signing a pact to become beholden to the business whims of a third party.
Good luck hosting an unmaintined piece of software though, there is no guarantee it will just instantly have community backing.
GitLab took external investments will have a liquidity event at some point. That means an acquisition or an IPO. Right now we're aiming for an IPO https://about.gitlab.com/strategy/#goals as we have since 2015 when we took the first external investment.
Change to Keybase git
Doesn’t get more neutral than private key encrypted source control