Skip to content

Comment on Status: Investigating reports of connectivity issues

Comments

Queue obtuse comment about how this is no big deal because git is distributed source control, ignoring the fact that Github != git and that issues/PRs/etc are pretty important.

Followed up by the comment that we need to stop this monoculture that we are creating and go back to mailing lists.

Which is then countered by people arguing that GitHub was the greatest thing to happen to open source and has introduced so many more people to the OSS community. Perhaps throwing in that a self hosted solution will most likely have worse uptime than GitHub does (which spawns it's own sub-thread of SaaS vs self-hosted solutions)

Then someone says that a higher barrier to entry could help the ecosystem (while muttering something about how many JS libraries there are out there).

I could keep going, but it seems github is working again for me, so off to do some work!

which spawns it's own sub-thread of SaaS vs self-hosted solutions

Our Github Enterprise instance sure has better uptime than Github itself. :)

also means that we cant composer install any project because even if the requirement is cached, each item is checked against github to see if the cached version should be invalidated :/ just took half an hour to complete an install...

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.