51–60 of 108 posts
Earlier quoted context omitted.
Yeah, because Gitlab would never go down. https://hn.algolia.com/?q=gitlab+down
Gitlab can be self hosted
Although I guess the benefit is that the CTO gets a psychological lift of looking over Jeremy from IT's shoulder when he tries to fix the issue rather than being at the mercy of some engineers which the company can't fire.
The fact that GitHub being down can have such an impact means that Git’s decentralised features don’t go far enough. Why aren’t issues, PRs and all these other little things we depend on also stored in a git repo? Or something similar that can withstand GitHub being down. I set aside time today to go through my notifications and I can’t because of this. Notifications are trickier to decentralise but still, ugh.
all I could say was, uhhhh github is a single point of failure. Unless you're mailing diffs around like Linus (which nobody I knew did), it's 6 of one, half-dozen of the other.
there are lots of great things about git and especially git over e.g. svn (especially merges) but I never bought the decentralization argument the way it was spearheading the conversation back then.
The fact that GitHub being down can have such an impact means that Git’s decentralised features don’t go far enough. Why aren’t issues, PRs and all these other little things we depend on also stored in a git repo? Or something similar that can withstand GitHub being down. I set aside time today to go through my notifications and I can’t because of this. Notifications are trickier to decentralise but still, ugh.
That being said, Fossil has what you want. Are you willing to switch?
The fact that GitHub being down can have such an impact means that Git’s decentralised features don’t go far enough. Why aren’t issues, PRs and all these other little things we depend on also stored in a git repo? Or something similar that can withstand GitHub being down. I set aside time today to go through my notifications and I can’t because of this. Notifications are trickier to decentralise but still, ugh.
With that in mind, your comment is similar to complaining about Jira being down, or Jenkins... they are different products.
The fact that GitHub being down can have such an impact means that Git’s decentralised features don’t go far enough. Why aren’t issues, PRs and all these other little things we depend on also stored in a git repo? Or something similar that can withstand GitHub being down. I set aside time today to go through my notifications and I can’t because of this. Notifications are trickier to decentralise but still, ugh.
The fact that GitHub being down can have such an impact means that Git’s decentralised features don’t go far enough. Why aren’t issues, PRs and all these other little things we depend on also stored in a git repo? Or something similar that can withstand GitHub being down. I set aside time today to go through my notifications and I can’t because of this. Notifications are trickier to decentralise but still, ugh.
Quick, activate the Copilot-based sysadmin!
The fact that GitHub being down can have such an impact means that Git’s decentralised features don’t go far enough. Why aren’t issues, PRs and all these other little things we depend on also stored in a git repo? Or something similar that can withstand GitHub being down. I set aside time today to go through my notifications and I can’t because of this. Notifications are trickier to decentralise but still, ugh.