I recently and very reluctantly switched from Ruby+Rails to Python+Django. I really preferred Ruby's syntax: to me, it's just prettier and cleaner than Python.

I recently and very reluctantly switched from Ruby+Rails to Python+Django. I really preferred Ruby's syntax: to me, it's just prettier and cleaner than Python. I really preferred Rails' organization: less flexible than Django means faster development when my projects fit into Rails' organization... ... but YKatz's article gives me comfort that I made the right decision. While you can accomplish many of the same bits of magic in Python, it's much harder to do so. Clearly, I'm not a Ruby ninja, but I am someone trying to get stuff done and the pervasiveness of monkey-patching in Rails bit me a number of times (track down some function only to find out that I was looking at the wrong, un-monkey-patched version). I hadn't really realized how much I don't miss Ruby until reading through YKatz's article on how Ruby 2.0 will handle monkey-patching. How about just making monkey-patching harder? Python has plenty of complexity, but you don't need to know about it: you can use Django just fine without paying much attention to the richness of Python. Ruby also has plenty of complexity and you need to know about it: use Rails or add a plugin to Rails and you'll quickly be reading through complicated Ruby classes that monkey-patch Rails.