Ruby Clouds: Engine Yard Vs. Heroku 41
snydeq writes "InfoWorld's Andrew Glover provides an in-depth comparison of Engine Yard and Heroku, two cloud-based, platform-as-a-service offerings for Ruby development. 'To put it simply, Heroku will appeal more to developers and Engine Yard will appeal to operations folks. Consequently, when evaluating the two platforms, one's choice usually comes down to what's more important: Heroku's rapid deployment via a hands-off infrastructure, or Engine Yard's total control over all aspects of application deployment, provisioning, and monitoring.'"
Re:Ruby?! (Score:4, Interesting)
Not to mention Ruby 1.9 is statistically the same speed as Python 3 (if not just very slightly faster).
I like both so I really don't care who wins this fanboy war.
My personal preference is Ruby since I have to work with Perl most of the day and Ruby is what OO Perl should be. Also I like RubyGems for library management, not having to worry about indentation, and there are some syntactic sugar in Ruby that gives it an edge (for me at least).
I like Python while using iPython to do some quick and dirty data checks with numpy and matplotlib.
Re:I must be missing something (Score:4, Interesting)
This. It's not specific to Ruby frameworks though. You're pretty much in the same situation if you want to use anything other than PHP+MySQL. Generic hosts nowadays are pretty much meant for non-programmers to run their own PhpBB, Wordpress, Drupal and various legacy websites, not recently developed web applications unless the developers are still stuck in 2004 and choose PHP+MySQL as their language and database even when they have the chance to start from scratch.
Personally I just get a XEN/KVM server somewhere and install what I need myself, be it Ruby+Rails, Node.js+Railway or Scala+Play and Redis, RIAK, MongoDB and/or PostgreSQL.