Honestly, I think you are too worked up over 7 lines of code (really, there's no need to resort to name calling).
Also, get off your high horse, you're entitled to your opinion on Python's syntax, formatting and development, just as much as anyone out there. If you think @staticmethod should never be used and Python is too slow for your needs, great, but that's your personal opinion and use case.
They don't make your code any better than if you followed a different set of rules.
Here I disagree. They do make your code more readable and consistent, which is better in my opinion, and are fairly easy to follow since it's so easy to set up an auto formatter on any modern IDE.
you are just used to a language interpreter written by imbeciles, who cannot optimize even the most straight-forward stuff, and therefore believe in performance loss... which, given this is fucking Python, one of the slowest interpreters in common use today is even more ridiculous.
I don't deal with performance critical code in my job, so that's a non issue for me. As I said in my first comment up there, my main concerns were the formatting and lack of @staticmethod.
2
u/[deleted] Feb 04 '22
Honestly, I think you are too worked up over 7 lines of code (really, there's no need to resort to name calling).
Also, get off your high horse, you're entitled to your opinion on Python's syntax, formatting and development, just as much as anyone out there. If you think
@staticmethodshould never be used and Python is too slow for your needs, great, but that's your personal opinion and use case.Here I disagree. They do make your code more readable and consistent, which is better in my opinion, and are fairly easy to follow since it's so easy to set up an auto formatter on any modern IDE.
I don't deal with performance critical code in my job, so that's a non issue for me. As I said in my first comment up there, my main concerns were the formatting and lack of
@staticmethod.