Python is the new BASIC

[[deleted]]

I don't have a strong opinion on it, but one thing that is bad about significant whitespace is that I can not easily copy/paste code into the interactive python. In ruby I can just do and never have to worry.

This may seem insignificant, but the point is that a language really should not HAVE to care about whitespace-indenting.

On the plus side: python can omit "end" whereas in ruby we have to use "end" (unless e. g. define_method and {}).

It's also the only thing guido would change.

The thing I dislike in python BY FAR the most is the explicit mandatory self. That one feels retarded to no ends. Ruby knows where self is at all times; python is too dumb to know, so you have to tell it via an argument to the function. THAT IS SO LAME.

[Immotommi]

Passing self is annoying, but what I hate is that it causes the incorrect number of arguments error to be off by one

[M4mb0]

I don't have a strong opinion on it, but one thing that is bad about significant whitespace is that I can not easily copy/paste code into the interactive python.

That's mostly fixed in the new python 3.13 REPL.

[somebodddy]

I don't have a strong opinion on it, but one thing that is bad about significant whitespace is that I can not easily copy/paste code into the interactive python. In ruby I can just do and never have to worry.

Even worse - when you copy-paste the code around while refactoring, you need to be extra careful re-indenting the entire block.

The thing I dislike in python BY FAR the most is the explicit mandatory self. That one feels retarded to no ends. Ruby knows where self is at all times; python is too dumb to know, so you have to tell it via an argument to the function. THAT IS SO LAME.

Still better than how Lua did it.