Yup...i can confirm that

The reason C becomes relevant to Python users isn't typically because the interpreter is written in C, but because so many important libraries (especially numpy) are implemented in C.

You then see people making scripts that take days to run, but it's fine, they're only going to use it twice and are busy enough to be able to wait

Sponsored by "terrible python code by Matt Parker"

I think the problems there are exacerbated a lot by over-eager type coercion and other crappy design decisions inherited from almost 30 years ago

[object Object]

!Reddit moment.!<

Operator overloads are excellent for readable code when used well - I object to their inclusion on this list.

Still easier to refactor than Python. ;-)

Perl is the only language that looks just as incomprehensible before and after a rot13 transformation.

Python on the other hand is the only language that will cause your application to stop working because you mixed up tabs and spaces, even though it looks perfectly fine on your scr.

And lisp is hard to say if you have one.

Edit: aa -> after a

I still write more Perl than Python these days.

For me it's dependency hell. Almost as bad as npm.

You can make embarrassing mistakes in virtually any programming language that's not too esoteric.

When I still used Python for prototyping (today, I usually use Go for that), it happened much too often that I did this:

if foo:
    bar()
   foobar() # syntax error

In Lisp, however, both errors are much harder to make (not even considering GNU Emacs's superb auto-indentation - which is what most Lispers use these days, as far as I know):

(when foo)  ;; <- obvious!
    (bar))

(when foo
    (bar)
          (foobar)  ;; <- still valid
(quux))  ;; <- also still valid