3 ms·
As with most language comparisons, the author is clearly established on one side of the fence and unwilling to investigate in any meaningful sense. He begins w
by req2 17y ago
As with most language comparisons, the author is clearly established on one side of the fence and unwilling to investigate in any meaningful sense.
He begins with a somewhat spurious statement on how code must be arranged, continues with a complete misunderstanding of what most people mean by scope, and then accuses Python of innumerable memory leaks and associated bugs before he even gets through his first set of comparisons. He claims Python dictionaries abuse the term 'immutable', but they most decidedly never make any such claim. You might learn something about Clojure, but take everything he says about Python with a grain of salt.
(Anyone who is interested in concurrent Python should check out multiprocessing, not threading.)