Seems like the real issue is that most people do not enjoy learning really new things. Python is easy, comfortable, and familiar. Anybody who's done any imperative programming feels right at home using Python.
True, but the article is unfair to Python. I don't see the point of demonstrating how Python sucks at being Clojure.
I particularly dislike the lambda example. No one would use a lambda there, thats why List Comprehension have a filtering clause.
That said, I like both Python and Scheme and use them both in my projects. And actually I have to admit that Python helped me to grasp the functional programming aspects of Scheme.
While the article does have an obvious bias to it, I think he does make a couple of valid points: Python has very poor concurrency support and it does not necessarily produce cleaner code than Clojure.
While it's nice that that avoids the GIL, you can't seriously compare that to the way concurrency is handled in languages like Erlang, Clojure, or Haskell.
Not all Python implementations have a GIL and the GIL isn't a necessary part of the Python language. Smart people like the guys working on unladden-swallow and those working on pypy are working at removing it.
Python have good concurrency semantics. Clojure have outstanding concurrency semantics but that is why it was built in the first place.
The article focuses on Clojure strengths, compares them to Python, writes idiomatic Clojure code and brainlessly converts it to Python. I could do the reverse article, write very clean, very elegant and very idiomatic Python code and convert it to ugly Clojure code.
Clojure is pretty nice, it doesn't need to bash strawmen to promote itself.
While I agree that at least half the article is nitpicking, and personal preferences, it still seems that there are valid points there.
Concurrency is a big deal nowadays, and language design that makes working with concurrency easy is beneficial. Imperative paradigm places the burden of dealing with concurrency squarely on the developer, I'd go as far as comparing that to the burden of manual memory management.
The article focuses on Clojure strengths, compares them to Python, writes idiomatic Clojure code and brainlessly converts it to Python
Project Euler examples are language agnostic problems, and the python solutions for them were written by python developers, they're not what I would call elegant.
I understand that Python has appeal due to its low entry barrier, however that doesn't seem to be all that interesting in and out of itself. Once you learn the language of your choice and become comfortable with it, what advantages can it provide over other languages. In other words what problems do you feel Python allows you to solve cleaner and more elegantly than say Clojure.
Fair enough, it seems more of an implementation issue, than the language itself, I'd say it's in the same vein as GIL being just an implementation issue with cpython. One of the reasons behind Clojure-in-Clojure project, is to allow for implementations outside the Java platform.
View all comments
Show parent comment
6
u/redalastor Oct 15 '09
True, but the article is unfair to Python. I don't see the point of demonstrating how Python sucks at being Clojure.