Slashdot Mirror
Ruby Clouds: Engine Yard Vs. Heroku
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.'"
I love Heroku's approach to offering a base tier for free. It makes it really simple of throw up a quick app at no cost (four or file commands) and it's dead easy to scale. It's expensive compared to self-hosting though (obviously) and there are some restrictions that chafe a bit now and then, but it's pretty cool!
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?
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.
These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
While I am a fan of both of these services, I really enjoy using openshift more. OpenShift is completely free and supports ruby, python, perl, java, and PHP.
For those who don't know, OpenShift is Red Hat's free platform as a service all running on top of RHEL.
--
I admit I am not a big follower of Japanese manga, that's why I probably never heard of Ruby Clouds: Engine Yard vs. Heroku, but is it any good?
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.
My other account has a 3-digit UID.
Probably.
I'm not sure how to feel about all of this. Not the comments from the Anon, but the Ruby situation. Some of the hate is about the language and I'll admit it, I'm not a fan of Ruby. OK, RoR, I see some of the benefits, Ruby on its own, well, just not a fan. I'll just leave it at that before I display any more stupidity and ignorance, just to say that the Anon above is right with the comment about folks not knowing much outside of the C universe. I certainly don't.
The rest of the hate comes from something else and that is an establishment that feels fear and intimidation when they think of a new crop of kids coming out of or migrating to NYC/SF/Boston/Etc. It may be based entirely on stereotyping, but any potential project I can think of, I can do a quick search on GitHub and find a Ruby variant or two or five on it. Couple that with the fact that some top schools are showing some love for Ruby and an unconscious bit of class warfare begins to show up.
When I think back to Ilya Zhitomirskiy, regardless of why he did what he did, I feel like a total shitbag. Me and hundreds of people here on Slashdot had nothing but negative things to say about his project. So yeah, there is a feeling of blood on my hands and that feeling stretches on to any fashionista comments about those who write Ruby.
Bah, enough rambling, that has just been on my mind for a few months now.
I agree with your second point, but not your first. Ruby is not a horrible language. On the other hand, I see no need to learn Ruby when I can already do everything I need in perl/php. I guess it's a simpler language though, at least from what I can tell. At least simpler than perl (not like that's a high bar). So I can see why some people would enjoy using it. Same with Python. I don't use it myself. Learned it, decided it was basically PHP only a little prettier.
All the world's a CPU, and all the men and women merely AI agents
Design a platform composed from the ground up as a collection of clean, interlocking modular blocks, Those blocks are designed to allow the developer to choose from a wide range of functionality and would be designed to make platform extensibility a natural process. As the library of functionality grew, 99% of the time you could just pull a few blocks out, connect them and you'd be off to the races. If you needed anything new or particularly esoteric, you could just create a new block, and when done add it to the library so others could enjoy the fruits of your labor in the future (as you enjoyed theirs now.)
I'm tired of looking at 20 different systems with 20 different sets of advantages and disadvantages. Make the app platform core module uber-tight and way fast (maybe something LISPish.) Create a simple abstraction module that provided a smooth and consistent interface so library modules could easily be written in or ported to any popular language. Of course there would be the classes of modules to support various file types and interactions, network protocols and interaction, maybe natural language or device dependent smart formatting, you could start with all kinds of goodies in the cupboard. Build the thing from the ground up to sit on a hardware abstraction layer that allows the application to leverage any and all hardware and network resources available to it. This would allow you to tune the beasty to its selected environment without the need of screwing with the platform engines configuration.
Is it just me, or isn't there now sufficient experience and information available both from the "using end" and the "designing end" to build a platform that is both flexible enough to assimilate new technology, fully utilize existing technology and provide basic services that most of us seem to be asking for on fairly regular basis. I'm not interested in religious wars. I just want to be able to slap something together without getting a doctorate in the silly thing or go through a 2 year learning curve because the tech keeps changing under my feet.
Then again maybe I'm just pissing and moaning to myself and a holy grail is just a silly myth. I'd be interested to see how others feel?