undefined | Better HN

0 pointsseoaeu4y ago0 comments

> For the past year, they have been down a couple of magnitudes more time than I have spent managing my server.

I have spent orders of magnitude less time feeding my pet rock than the average dog owner spends feeding their pet.

The difficulty of keeping a service online depends on what it actually does. Not to mention, outages are generally caused by making changes. Changes which are required if a service is going to continuously improve

0 comments

AshamedCaptain4y ago

If you are trying to make the point that Github.com is the only "non-pet-rock" web-based project managament and bug tracking system available (for selfhosting or not), well, that is just false. The alternatives have at least as many features, if not more. Some of them even predating Github.com by decades.

If you are again trying to make the point that they have a bazillion times the load, I will say again that it is self-inflicted, and thus part of the problem, and not a valid excuse nor justification. Other providers do not seem to have these problems anyway.

seoaeuOP4y ago

Comparing uptime between comparable services is reasonable. (Though I will say that having used some GitHub competitors, counting the number of features really overlooks the actual user experience between them.)

Comparing uptime between a production service and a single personal server however isn’t reasonable. You haven’t even said what your server actually does, only that it rarely goes down!

fartcannon4y ago

His point is that if everyone had their own server, everyone would have better uptime than they currently get using github.

The complexity and load of github is the problem.

1 more reply

rightbyte4y ago

If you self-host you are in full control on when to do changes that has potential to mess up and can do them on a convenient time.

j / k navigate · click thread line to collapse