61–70 of 108 posts
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.
Earlier quoted context omitted.
>what are you going to do better than github? Not add new features every week? Seriously, you cannot tell me that you cannot run a minimal version of a git repo service much more stable than that. I blame the need for new shiny stuff.
> I blame the need for new shiny stuff. Ya'll make me laugh. Don't add any features and "This thing is dead, nothing new in years, find an alternative" But a company actively adds new features their customers are asking for and you're upset that they're adding new features. Pick a lane.
Earlier quoted context omitted.
It depends on your needs and team size. For few tens of dev that need a versioning system with some sugar, a self hosted gitlab can acieve better uptime.
> a self hosted gitlab can acieve better uptime. Gonna call BS on that. It can achieve better uptime, if you ignore the downtime for upgrades, the downtime for configuration errors, the downtime when the disk fills up...
Btw, you cannot compare a scheduled maintenance window with an unplanned downtime ... maybe in the middle of an important deployment.
Earlier quoted context omitted.
> a self hosted gitlab can acieve better uptime. Gonna call BS on that. It can achieve better uptime, if you ignore the downtime for upgrades, the downtime for configuration errors, the downtime when the disk fills up...
As I said, it depends on your needs. I don't know if you have ever managed a small gitlab self-hosted installation, but it's really trivial, you set up it the first time, and you forget about it. Also, the upgrade process takes few minutes to complete. Btw, you cannot compare a scheduled maintenance window with an unplanned downtime ... maybe in the middle of an important deployment.
Bitbucket Server
Earlier quoted context omitted.
It depends on your needs and team size. For few tens of dev that need a versioning system with some sugar, a self hosted gitlab can acieve better uptime.
> a self hosted gitlab can acieve better uptime. Gonna call BS on that. It can achieve better uptime, if you ignore the downtime for upgrades, the downtime for configuration errors, the downtime when the disk fills up...
Besides the last one, the others you can schedule when developers are not actually working on something, or give a headsup so developers can be prepared in case of errors.
In the case of GitHub, Microsoft deploys changes whenever they want, whenever you want it or not.
Earlier quoted context omitted.
DNS. It's always DNS
When in doubt, and the outage is widespread it's either DNS or BGP, most likely DNS. My money is also on DNS in this case.
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.
heh, this was my argument back in like 2009 when everyone was all, "DECENTRALIZED!! We have to take months to migrate from SVN to git cause DECENTRALIZED!! You don't one a single point of failure do you?!" 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…
I would say the decentralised features of git work for me. And they are no overblown.
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.
Those who use it by emailing patches around aren't affected, ala the linux kernel.
Earlier quoted context omitted.
>what are you going to do better than github? Not add new features every week? Seriously, you cannot tell me that you cannot run a minimal version of a git repo service much more stable than that. I blame the need for new shiny stuff.
> I blame the need for new shiny stuff. Ya'll make me laugh. Don't add any features and "This thing is dead, nothing new in years, find an alternative" But a company actively adds new features their customers are asking for and you're upset that they're adding new features. Pick a lane.