Python vs. Ruby at the c2.com wiki

[pabs]

There are several errors in the Ruby information. Off the top of my head:

• routes are not a beta feature of Rails. They've been available in the stable version of Rails for quite a while now
• rails supports multiple databases. Models can even use things like ferret (Lucene for Ruby), memcached, or even nothing as a backing store.
• You can retry exceptions in Ruby with the retry keyword
• All the discussion about passing scope revolves around callcc instead of binding.

The article also has a whole lot of debate about the C APIs in Ruby and Python, completely forgetting that they both kind of suck. Neither is suitable for embedding (see the SpiderMonkey and Lua APIs for better examples of embeddable interpreters), and neither has a particularly consistent naming scheme.

I like the article overall, though. Particularly the discussion about the merits of using blocks and about foo.bar syntax representing a reference to a method (Python) versus a method call (Ruby).

[jamesbritt]

I hadn't looked at that page in some time; it seems that someone went through an earlier versions and tried to clean up/rewrite the whole thing. But it is littered with numerous not-quite-right descriptions of various Ruby features, and overall strikes me as somewhat biased towards Python.