Like a Stanford dorm room on steroids, our Sunnyvale office is 40,000 square-feet of Bay Area badassery, brimming with some of the biggest brains on the planet, dreaming up digital masterpieces and keeping time in agile sprints
Because... yuck. I get what you're going for, but I'm sure you can do better.
Using them for hosting your site? Double-cringe.
Social responsibility: Am I supporting a company that relies on horrible and sexist and demeaning ads to get attention?
Social cachet: Would I be embarrassed to have people find out who I was using for my domains/hosting? It may be shallow, but working with GoDaddy looks as sophisticated as having an @aol.com email address.
I'm sure there are other things that could be added.
They've since recanted their SOPA support, but I think it'll take more than a calculated business move to regain any consumer trust. Personally, I'd advise being familiar with the organizations that have ever supported SOPA, and cutting ties with them for any future endeavors:
Here are some previous mentions of GoDaddy/SOPA on HN:
Their past ad campaigns have been very trashy and sexist as well.
Their pricing is higher than other registrars, unless you play their discount/coupon games.
In my experience a few years ago the process of transferring away from GoDaddy took as long and was as complicated as it possibly could be by law. Like absolute limit. If they were able to send me harassing emails before the transfer was completed, they did. Link bating with anti-agreements. I stuck it out for months jumping through every hoop they raised because I wanted to transfer away that badly. Maybe things have improved.
I hate GoDaddy.
But, yeah, I wouldn't use them for hosting anything.
This is making the assumption that only someone who was quite new to Ruby (and development in general) would use GoDaddy for hosting.
So yes, I doubt anyone is still using GoDaddy for Rails hosting.
"If you have Java enabled for your hosting account, it will conflict with Rails."
"Currently, Rails version 1.1.6 is supported in the default directory, while Rails 2.2.2 is considered an alternate "development" environment"
I don't really blame GoDaddy, since their shared hosting infrastructure is just not built for long-running processes. For rails, CGI is laughably slow, and FastCGI, while faster, still wasn't performant enough and was causing intermittent 500 errors.
I ended up converting the entire project to static HTML (getting rid of the rails CMS component) and it was smooth sailing from there. Thankfully the client required very few updates to the site after that (otherwise I might have tried to move it onto Drupal or something).
My life is better for it too, I felt really agitated every time I had to touch Ruby code.