[eladmeidar]

I will not go into a "he said she said" kind of thread, but i really had no intention of making it something like it actually came to.

Yeah it's a small team and a very talented one, you are right. but graphs and ajax? this is what you pay for? or you actually want the basic service to work as expected?

[jackowayed]

In a simplistic sense, yes, you are paying for graphs and ajax.

You can host git repos very cheaply on a random server. You can probably even make it work on shared hosting.

You pay for GitHub for a very convenient and pretty web interface (which is pretty well exemplified by "graphs and ajax"). Permissions on private repos are easy. You can look at code, commits, blames, etc in ways that your eye can parse easier. Graphs let you see some cool-but-probably-unimportant data. Your newsfeed tells you what's going on on repos you care about.

None of that's essential. You can see blames by typing `$ git blame <file>` at your favorite shell. But it's way uglier and doesn't show you blocks of lines that were last changed at the same time as intuitively.

Then you also get GitHub pages and a few other things like that, but it's pretty easy to setup jekyll on your own.

Basically, you just pay for a lot of small conveniences that add up to being worth not setting it up yourself and losing the better interface.

[grandalf]

I do, but the outages have not imapacted me since I keep a local backup (I also haven't needed to do any deploys during the brief outages).

I could host git repos cheaper than github with a $20 slice over ssh. So yes I pay extra to github for the additional features.

Edit: I also enjoyed reading about Github's custom stuff (like bert/ernie)... clever stuff that most teams would determine wasn't worth the effort, but that has worked very well for github.