Ruby Clouds: Engine Yard Vs. Heroku

Posted by samzenpus on Thursday December 1, 2011 @01:08AM from the silverest-lining dept.

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.'"

1 of 41 comments (clear)

Min score:

Reason:

Sort:

Re:Ruby?! by matthewmacleod · 2011-12-01 01:31 · Score: 5, Insightful

Literal nonsense - how can a language be crippled without a framework written in it? There are other web frameworks for Ruby, and it's perfectly usable as a standalone language with a nice big library. Ruby's a great scripting language, much like Python: concise, flexible and readable. The off-the-shelf interpreter can be slow, but that's improving and there are alternatives. So what's horrible about it?