3 ms·
It’s not really lack of repo access that makes GitHub outages bad. It’s all the “value-add” stuff on top of the repo that makes outages suck. You’ve got workfl
by spookthesunset 5y ago
It’s not really lack of repo access that makes GitHub outages bad. It’s all the “value-add” stuff on top of the repo that makes outages suck.
You’ve got workflows bolted on top that block forward progress when it goes down. Hooks for when push requests happen, when commits happen, etc. You’ve got code reviews in your workflow that cannot happen when the service is down.
Basically there is much more to a service like GitHub / gitlab than just “write code, commit”. These services enable powerful workflows. When those go down all you can do is write code locally. The rest of the pipeline is dead in the water, which in many cases makes your overall ability to work virtually impossible.
- oblio 5y agoAnd it's going to be the same with cryptocurrencies. All the interesting stuff for normal people is built on top.
- 0ldskool 5y agowell the case is that if github keeps going down and becomes completely unreliable you can take your decentralized code and more it to a different provider. Those other providers will also have value added stuff and you will not lose the core of your business/work (your source code). If it was a pure central authority + protocol you would be doomed to live and die with them. Imagine if instead of git + github you had some source code protocol that only allowed you to checkout the latest commit of some branch. All code history needed to be viewed by connecting to the central servers. Why not make it even worse, you could only view+edit a specific file of the latest commit on your machine. All other files must live on the central server, you are not allowed to build/compile code locally either... Centralization is the process of you giving up control to a "trusted" entity. If they fail you lose everything
- oblio 5y agoOk... how does that help cryptocurrencies, though?