←back to thread

Days since last GitHub incident

(github-incidents.pages.dev)
212 points AquiGorka | 2 comments | 11 Dec 25 16:52 UTC | HN request time: 0s | source
Show context
queuebert ◴[11 Dec 25 18:16 UTC] No.46234915[source]▶
At this point, is there any downside to switching to GitLab?
replies(4): >>46234937 #>>46235057 #>>46235171 #>>46235347 #
1. loloquwowndueo ◴[11 Dec 25 18:19 UTC] No.46234937[source]▶
What’s gitlab?

(Snarky way of saying: GitHub still has huge mindshare and networking effects, dealing with another forge is probably too much friction for a lot of projects)

Not that GitHub doesn’t suck…

replies(1): >>46235479 #
2. burningChrome ◴[11 Dec 25 18:55 UTC] No.46235479[source]▶
When GitHub was bought by Microsoft, Gitlab made moving your repos to them super easy. Apparently not enough people have moved and it would seem even with sustained attacks from all kinds of different vectors, it would seem people continue to stick with them.

I use both Gitlab and Github and have yet to experience any downtime on any of my stuff. I do however, work at a large corporation and the latest NPM bug that hit Github caused enough of a stir where it basically shut down development in all of our lower environments for about two weeks so there's that.

But I do agree, and it seems like their market share increased after the Microsoft acquisition which is contrary to what I heard in all my dev circles because of how uncool MSFT is to many of my friends.