- It is hard to read, because it is missing semicolons and braces.
- Indentation as a syntactical element is just silly. This takes away freedom from the developer and makes the code less readable without any benefit.
- Indentation-dependant scopes make multiple statements on one line look horrible.
- Doc comments
- They use triple quotes which doesn't make sense for a comment.
- They go under what they are documenting, which looks wrong and is very unusual.
- They are technically not comments, which is a terrible idea.
- They are accessible at runtime, but shouldn't since this encourages spaghetti code.
defkeyword does not imply a function, so one may think it is declaring a variable, or something else.
- Strange naming
__add__looks like an internal function. That these define operators looks like someone was too lazy to do this properly (yet again!).
- Exception handling using
exceptinstead of the usual
catch. There is literally no point to do this, and it confuses users.
- Same goes for
else if. This is just pointless, and again looks like a lazy implementation.
- Strange symbols
orinstead of the more conventional and cleaner looking
elsestatements are not expressions. If they were, the additional ternary operator syntax would be completely redundant, and the code would be cleaner.
- The syntax for inheritance looks really confusing.
Foohas a constructor that takes a
Baras an argument, and not like
- For some reason, the
passkeyword exists. Why can't we just leave the block empty or omit the
:? Yet another lazy implementation!
- The recently added
:=(assignment expression) operator exists, instead of simply making the normal assignment (
=) an expression.
Falseare capitalized which is unconventional and annoying.
- Functions can have named arguments like
foo(bar=baz)which looks strange, and instead functions should just take dictionaries instead like
- Lambdas are a poorly implemented afterthought.
- There is absolutely no
switchstatement or anything along those lines, leading to absolutely HUGE
- Intepreters lead to runtime errors which could otherwise be detected at compile time. This often causes bad errors to make it into production due to untested edge cases.
- Very bad performance.
- Python is hard to package. Of course tools exist that can do it, but they are slow and large as they always include the interpreter as opposed to compiling the code or using some sort of faster intermediate language. Packaged python also includes the source code, which may be undesirable.
- Passing an invalid type into a function may cause unpredictable behaviour. Manual type checks are annoying, and type hints are still just hints.
- It is often unclear what type a function is expecting, thus it can be hard to know how to call it, especially if it is undocumented.
- A function can return whatever type it wants, so it is hard to work with and unpredictable.
- Variables don't need to be declared. This leads to many issues, such as accidentally overwriting other variables with the same name, or typos going undetected.
- A variable's type may be changed after its assignment, making it harder to work with.
Poorly done Classes
selfparameter being passed into functions explicitly is pointless boilerplate. Instead it should just be there implicitly, and static functions should be declared with a keyword such as
- Fields do not need to be declared. This leads to issues mentioned before. It also makes the data a class stores undefined, making it harder to work with. It is recommended to declare fields, but unfortunately not enforced.
- Enums are basically just classes, and are yet another lazy afterthought.
Wide Spread Because Of The Wrong Reason
- Python is seen as "the beginner's language", and it really should not be. As said earlier on this website, Python has numerous issues that stop the newbie from quickly getting used to other PLs, by lacking basic functions.
- Python should only be used if you wanna handicap yourself into an inferior PL, just to see what you can do. No more, no less.
- Strings can be evaluated as code, also encouraging spaghetti code.
- Doc comments are available at runtime using
help(element), and they should not be, because this too encourages spaghetti code.
- The command line REPL prints
Use exit() or Ctrl-Z plus Return to exitfor no reason, instead of simply exiting.
- Operator chaning often works in completely nonsensical ways. For example
False == False in [False]is treated as
False == False and False in [False]and not as something that makes sense such as
(False == False) in [False]or
False == (False in [False]).
Python is a bad programming language that no one should use. Please don't hesitate to quit using programs made in Python. If you continue using them, it will motivate the Python devs to keep making this garbage, plus programs written in Python are usually VERY slow. And NEVER, EVER, EVER, EVER use Python in your own programming shenanigans. It's YOUR project. You have full control over it. Why even use Python if that's the case?
And, one more thing:
Please spread the site so more people know the truth. It would mean the world to me. Thanks.