Replacing github gems w/ gemcutter is a mistake
It’s been two weeks since github dropped their gem support for gemcutter, and it’s been one annoyance after another (gems being out of date and not being able to fork, mostly). I see no value in the separation of code and gem hosting (and I’ve been kinda surprised at the bandwagon gathering over how great this is).
So no offense @qrush — gemcutter is cool, and has it’s place —, but I’m asking someone to try and put me in place with respect to why this was a good idea. Because until someone does, I’m going to jump on the anti-bandwagon: @github, please bring back gem building/hosting.
