Comments on: Engine Yard And GitHub Transition http://www.engineyard.com/blog/2009/engine-yard-and-github-transition/ Wed, 08 Feb 2012 12:12:12 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jeff P http://www.engineyard.com/blog/2009/engine-yard-and-github-transition/comment-page-1/#comment-37836 Jeff P Thu, 26 Nov 2009 20:24:56 +0000 http://www.engineyard.com/blog/?p=2026#comment-37836 @Dave, Lot more than $20k, probably more like $50k. They are very expensive, and the problem is it doesn't really buy you much, the rolls royce of cloud computing is sortof a joke. @Dave,

Lot more than $20k, probably more like $50k. They are very expensive, and the problem is it doesn't really buy you much, the rolls royce of cloud computing is sortof a joke.

]]> By: Troy Davis http://www.engineyard.com/blog/2009/engine-yard-and-github-transition/comment-page-1/#comment-18740 Troy Davis Wed, 16 Sep 2009 15:14:34 +0000 http://www.engineyard.com/blog/?p=2026#comment-18740 Curious: No, not accurate. It was a trade of services for visibility, not a down payment on future business. That's the nature of an at-will agreement. They both did their part and grew because of it. Curious' trolling aside, anyone who has watched Github for more than a month knows the level of engineering they do (erlang gitd, pages/jekyll, gist, FI). They're incredibly committed, and speaking as a customer, my value per subscription dollar is incredibly high. Given the one-of-a-kind scaling problems I'm sure they've encountered, I'm amazed it's been as responsive and stable as it has. We push and pulling constantly, and 99% of the time, it's snappy.Curious: No, not accurate. It was a trade of services for visibility, not a down payment on future business. Both parties grew because of it. Curious' trolling aside, anyone who has watched Github for more than a month knows the level of engineering they do (erlang gitd, pages/jekyll, gist, FI). Given the one-of-a-kind scaling problems I'm sure they've encountered, I'm amazed it's been as responsive and stable as it has. We push and pulling constantly, and 99% of the time, it's snappy. They're incredibly committed, and speaking as a customer, my value per subscription dollar is incredibly high. As for the social element, read the Web site: social code hosting. Some of us enjoy meeting in person, too -- I'd sure attend a meetup in Seattle. Curious: No, not accurate. It was a trade of services for visibility, not a down payment on future business. That's the nature of an at-will agreement. They both did their part and grew because of it.

Curious' trolling aside, anyone who has watched Github for more than a month knows the level of engineering they do (erlang gitd, pages/jekyll, gist, FI). They're incredibly committed, and speaking as a customer, my value per subscription dollar is incredibly high. Given the one-of-a-kind scaling problems I'm sure they've encountered, I'm amazed it's been as responsive and stable as it has. We push and pulling constantly, and 99% of the time, it's snappy.Curious: No, not accurate. It was a trade of services for visibility, not a down payment on future business. Both parties grew because of it.

Curious' trolling aside, anyone who has watched Github for more than a month knows the level of engineering they do (erlang gitd, pages/jekyll, gist, FI). Given the one-of-a-kind scaling problems I'm sure they've encountered, I'm amazed it's been as responsive and stable as it has. We push and pulling constantly, and 99% of the time, it's snappy. They're incredibly committed, and speaking as a customer, my value per subscription dollar is incredibly high.

As for the social element, read the Web site: social code hosting. Some of us enjoy meeting in person, too — I'd sure attend a meetup in Seattle.

]]> By: Jeremy Weiskotten http://www.engineyard.com/blog/2009/engine-yard-and-github-transition/comment-page-1/#comment-18672 Jeremy Weiskotten Tue, 15 Sep 2009 20:56:04 +0000 http://www.engineyard.com/blog/?p=2026#comment-18672 <a href="http://github.com/blog/493-github-is-moving-to-rackspace" target="_blank">http://github.com/blog/493-github-is-moving-to-ra...</a> http://github.com/blog/493-github-is-moving-to-ra…

]]> By: Jeremy Weiskotten http://www.engineyard.com/blog/2009/engine-yard-and-github-transition/comment-page-1/#comment-18671 Jeremy Weiskotten Tue, 15 Sep 2009 20:55:35 +0000 http://www.engineyard.com/blog/?p=2026#comment-18671 In case you missed it, GitHub has a blog post explaining (in great detail) their move to Rackspace. In case you missed it, GitHub has a blog post explaining (in great detail) their move to Rackspace.

]]> By: Jarin Udom http://www.engineyard.com/blog/2009/engine-yard-and-github-transition/comment-page-1/#comment-18661 Jarin Udom Tue, 15 Sep 2009 01:06:01 +0000 http://www.engineyard.com/blog/?p=2026#comment-18661 Seems pretty straightforward to me. I've met some of the folks at Engine Yard and they are solid people. The folks at GitHub seem the same way. There's just a point where it no longer makes sense to keep giving away valuable services for free. Seems pretty straightforward to me. I've met some of the folks at Engine Yard and they are solid people. The folks at GitHub seem the same way. There's just a point where it no longer makes sense to keep giving away valuable services for free.

]]> By: Leah Silber http://www.engineyard.com/blog/2009/engine-yard-and-github-transition/comment-page-1/#comment-18654 Leah Silber Mon, 14 Sep 2009 20:02:44 +0000 http://www.engineyard.com/blog/?p=2026#comment-18654 Thanks Luke! We're doing our best, as I'm sure are they :) Thanks Luke! We're doing our best, as I'm sure are they :)

]]> By: Leah Silber http://www.engineyard.com/blog/2009/engine-yard-and-github-transition/comment-page-1/#comment-18655 Leah Silber Mon, 14 Sep 2009 20:02:30 +0000 http://www.engineyard.com/blog/?p=2026#comment-18655 Thanks for the kind words Dom. We do our best, and you're absolutely correct: this move was made with a lot of planning and thought by both GitHub and Engine Yard. We're confident it'll all work out for the best :) Thanks for the kind words Dom. We do our best, and you're absolutely correct: this move was made with a lot of planning and thought by both GitHub and Engine Yard. We're confident it'll all work out for
the best :)

]]> By: Bill Mill http://www.engineyard.com/blog/2009/engine-yard-and-github-transition/comment-page-1/#comment-18578 Bill Mill Sat, 12 Sep 2009 22:43:19 +0000 http://www.engineyard.com/blog/?p=2026#comment-18578 > "why would Github choose to go elsewhere instead of pay Engineyard?" Well, presumably they felt they could get more service for less money than EY were offering, elsewhere. Why should it be anything more complicated than that? > "why would Github choose to go elsewhere instead of pay Engineyard?"

Well, presumably they felt they could get more service for less money than EY were offering, elsewhere. Why should it be anything more complicated than that?

]]> By: xyz http://www.engineyard.com/blog/2009/engine-yard-and-github-transition/comment-page-1/#comment-18548 xyz Sat, 12 Sep 2009 19:02:21 +0000 http://www.engineyard.com/blog/?p=2026#comment-18548 The key phrase is "I believe there were never hard feelings on either side". I'm not convinced that that is 100% accurate. The key phrase is "I believe there were never hard feelings on either side".

I'm not convinced that that is 100% accurate.

]]> By: joevandyk http://www.engineyard.com/blog/2009/engine-yard-and-github-transition/comment-page-1/#comment-18532 joevandyk Sat, 12 Sep 2009 17:57:41 +0000 http://www.engineyard.com/blog/?p=2026#comment-18532 Perhaps they want to manage their own servers and software. At a certain scale that becomes cost-effective. Perhaps they want to manage their own servers and software. At a certain scale that becomes cost-effective.

]]>