4 ms·
The compute part is the least of your worries, even installing the software is usually not your primary concern - everything is fine as long as you're on the ha
by Xylakant 6y ago
The compute part is the least of your worries, even installing the software is usually not your primary concern - everything is fine as long as you're on the happy path.
Software needs to maintained, patched, backed up, verified etc. It has bugs, security issues, hardware breaks in weird ways. This takes time and skill - ideally you'd need two or three people that are capable of fixing problems with the install. (one ill, one on vacation, one available). This is something that detracts from the actual work you're doing. I'm very much an ops person and I actually like tinkering with a gitlab install - it's just so many moving parts that I prefer not to run this for my company since it would eat a substantial chunk of my time just caring for this.
- mcguire 6y agoThe bottom line is that it is cheaper to use GitHub and live with the external risks than to maintain internal services or live without them. I note that the Linux kernel lived with bare Git for many years.
- Xylakant 6y agoAt least for small to medium organizations without specific reasons for self-hosting. Once you have a team that manages internal infrastructure, this calculus can change. The Linux kernel is a very specific case with a very specific development model that likely doesn’t apply to most other projects.