Skip to main content

RuPy, Snakes and Rubies, Night and Day

What is going on?

All around me I see people relating Python and Ruby. The communities seem somehow intertwined with their users, usages, and publicity. It seems like you can never find a blog that talks about one without the other, or a new frontier being tested by one of the "new" languages and not being explored by its counterpart. Where do people see this distorted similarity between two languages that are as different as night and day?

To Rubyist out there, don't take offense. I have far more experience with Python, than with Ruby, so I might sound biased. Please, take this as an honestly unbiased opinion. I'm just talking from the middle in this case.

Python stands out from most of the other languages around. Largely it is understood as "the language without brackets", but it is not entirely alone there. Ruby almost appears like a language extremist. Their core types have fifty million methods each, because if you expect it to be there, it should be there. Python is important, because it explores the methods a language can encourage good coding practices onto developers. Ruby is vital, because it explores interesting constructs like continuations and compact code forms utilizing their quirky syntaxes. Both might have their place, but they are far different places. Python is unassuming. It will take nothing for granted, such as not taking for granted that you wanted a method call, not a call to a function in some method. Ruby is assuming. It understands the difference between objects and types, just based on the casing of the name.

Fuzzyman states a similarity between the languages, but can this be taken as anything more than common usage? We can see an assumption of similarity across both communities, but nothing really ties them together anymore than any languages are connected by virtue of all being languages.

I've been known at times to seem like a Python zealot and anti-PHP/Perl/Ruby, but in this case I'm setting that aside and I want to state very clearly: these two languages are not similar. They are very different beasts, with more differences than anything else. The illusion of a relation between Ruby and Python only harms both of them. We have people asking for continuations in Python constantly, when they are a great idea in Ruby, but would not likely work well in this very different environment. Rubyist get attacked by a barrage of Rails killing Python projects, trying to take their steam.

Shouldn't we go our separate ways?

Comments

Anonymous said…
Can't we just all love one another? ;-)

They're different.. they're different. but they do share a lot of similarities. And I love the cross-pollination that's going on, and the competition is helpful for both communities as long as it doesn't devolve into mean-spirited bickering.

The request to get continuations, even if it might be largely irrelevant (I think you have a point) is a good example of the challenges that will help Python (and Ruby) gain new converts and ultimately improve.

So while I think your post was really about "why can't we all get along", it bears repeating: this is good stuff, so long as we get along while we're doing it. Like Windows and Linux, the competition improves both platforms, unless the competition becomes unfair.

(And, to all the Python people out there, we already know who's winning.) (And, to all the Ruby people out there, we already know who's winning.)

;-)

-j
Anonymous said…
I think your examples indicate two answers. Python's principles of easy code-reading means keeping out continuations. In this way, Ruby and Python should stay separate.

I think the copying of Rails into Turbogears, Django, etc. is related to the problem space: both Ruby and Python are used on the web where MVC projects create similar problems (maintaining templates, etc).

In fact, I think a lot of the cross-polination is going on in the web application problem space.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro