3 ms·

From our perspective, it was a matter of helping our partner and the Ruby community succeed. We're working really hard to make Ruby on Rails succeed. This is j

From our perspective, it was a matter of helping our partner and the Ruby community succeed. We're working really hard to make Ruby on Rails succeed. This is just one of the many ways that we've pitched in to help it do so. If, during that downtime, when the "Twitter's problems are Ruby on Rails" FUD was running high, would anyone believe that a Github scale failure wasn't a Ruby on Rails problem? We weren't willing to test it, so we solved the problem, i.e. we put our money where our mouth is -- That Ruby on Rails scales just fine, the bottlenecks are generally elsewhere.

davidw 17y ago
> From our perspective, it was a matter of helping our partner and the Ruby community succeed. I suppose what seems confusing to me is that there are a lot of things you could do to help your customers succeed, but many of them are fairly expensive - such as cutting your rates, or doing high end development work. With more basic hosting, say EC2, I know that Amazon isn't going to do beans for me, so I'm on my own. I know exactly what the price does and doesn't include, and what I have to provide myself. EY seems fuzzier... it's almost like having an extra developer on staff in terms of talent, but it is and it isn't: you can't tell that person to go off and do something else. Say I move one of my sites to EY; is your "whatever it takes" attitude going to include fixing up my ugly design/graphics work?:-)
- nakajima 17y ago
  It seems to me that the patch wasn't for "GitHub, the EngineYard client", but instead, "GitHub, the Ruby community resource", just as they support JRuby, Rubinius, and Rails development. If you operated a site that EngineYard saw as a valuable resource for the Ruby community, I'm sure they'd help you out in whatever way possible as well.
  - davidw 17y ago
    What you describe is that paying customers subsidize 'community resources', which is great for me as a mooching Rails (and github) user, but perhaps not so great for paying customers. I don't think they'd put it that way; and indeed I believe they must provide a lot of 'extras' for their customers for the cost of that service. Still though, it seems that it's a service that will be best with clients who make a lot of help requests, getting their money's worth.

davidw 17y ago

> From our perspective, it was a matter of helping our partner and the Ruby community succeed. I suppose what seems confusing to me is that there are a lot of things you could do to help your customers succeed, but many of them are fairly expensive - such as cutting your rates, or doing high end development work. With more basic hosting, say EC2, I know that Amazon isn't going to do beans for me, so I'm on my own. I know exactly what the price does and doesn't include, and what I have to provide myself. EY seems fuzzier... it's almost like having an extra developer on staff in terms of talent, but it is and it isn't: you can't tell that person to go off and do something else. Say I move one of my sites to EY; is your "whatever it takes" attitude going to include fixing up my ugly design/graphics work?:-)

nakajima 17y ago
It seems to me that the patch wasn't for "GitHub, the EngineYard client", but instead, "GitHub, the Ruby community resource", just as they support JRuby, Rubinius, and Rails development. If you operated a site that EngineYard saw as a valuable resource for the Ruby community, I'm sure they'd help you out in whatever way possible as well.
- davidw 17y ago
  What you describe is that paying customers subsidize 'community resources', which is great for me as a mooching Rails (and github) user, but perhaps not so great for paying customers. I don't think they'd put it that way; and indeed I believe they must provide a lot of 'extras' for their customers for the cost of that service. Still though, it seems that it's a service that will be best with clients who make a lot of help requests, getting their money's worth.