this post was submitted on 08 Jun 2025
353 points (97.3% liked)
Programmer Humor
36257 readers
881 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Partially unrelated to the meme, but I find it almost malicious how some python keywords are named differently from the nearly universal counterpart of other languagues.
This/self, continue/pass, except/catch and they couldn't find a different word for switch so they just didn't implement it.
It's as if the original designers purposefully wanted to be different for the sake of it.
Python does have a
switchstatement now, actually. And yes, they went out of their way to call it something different -match.https://docs.python.org/3/tutorial/controlflow.html#match-statements
PHP naming "::" a Paamayim Nekudotayim is also pretty infamous.
When I'm designing shit, I'm pretty zealous about borrowing terminology from anything even vaguely related to avoid this.
pass and continue are absolutely not equal (pass is a noop, and python has a continue keyword that does what you think), and switch is called match like in many other languages. except is weird though.
"except" is also used in Pascal (or at least the main derivatives of it), but not sure if that's older than its use in Python or not.
I read that
selfas a keyword also has quite a history. It was already used in Smalltalk, an OOP language from the early 80's.Isn't self not actually a keyword? Like you can name the first variable in a class method anything and it will behave like self.
You could use "this" instead of "self". And if you want a lynch mob of Python programmers outside your house, make a push request with that to some commonly used package.
I think there will be a lynch mob of git users outside your house for calling PR as "push request".
only github users. git itself doesn't have PRs, and other forges call them different things. gitlab calls them merge requests, pico calls them patch requests...
I've been wondering about the noise.
Edit: turns out, they weren't there to lynch me. They just gave me a two hour lecture on proper usage of git.
TECHNICALLY, there is no such thing as a pull request in git. That's a Github convention. It's really a merge request
e: drat someone already out-pedantic'd me
You could even choose the name this.
Iv come to loathe the "pythonic way" because of this. They claim they wanted to make programming easier, but they sure went out of their way to not follow conventions and make it difficult to relearn. For example, for me not having lambdas makes python even more complex to work with. List operations are incredibly easy with map and filter, but they decided lambdas weren't "pythonic" and so we have these big cumbersome things instead with wildly different syntax.
If the conventions suck you have to break them. How else can you improve things?
map and filter are almost always inferior to generators and comprehension expressions in terms of readability. If you prefer the former, it’s just because you got used to it, not because it’s better.
Speaking of big cumbersome things with wildly different syntax have you tried a ternary operation in python lately? Omg that thing is ugly. JavaScripts is hard to beat.
uglyTernary = True: if python_syntax == “shit” else: False prettyTernary = javascript_syntax == “pretty” ? true : false
That’s just because you’re used to it. The pythonic ternary is structured like spoken language, which makes it easier to read, especially if you nest them.
Is there an objective argument for the conventional ternary, other than „That’s how we’ve always done it!“?
I don't read spoken language, but I do read written ones. The problem with python's ternary is that it puts the condition in the middle, which means you have to visually parse the whole true:expression just to see where the condition starts. Which makes it hard to read for anything but the most trivial examples.
The same goes for comprehensions and generators
Maybe I'm missing something, but:
a lambdo which can only contain one expression, and not even a statement is pretty much useless. For anything nontrivial you have to write a separate function and have the lambda be just a function call expression. Which completely defeats the point
So much Python criticism comes from people who don't know the language.
I mean, there is a lot wrong with it, but every language has its quirks. Generally I like discussing it's actual flaws cause it helps me better understand the language.
And switch cases (called match cases) are there as well.
I use lambdas all the time to shovel GTK signal emitions from worker threads into GLib.idle_add in a single line, works as you'd expect.
Previous commenters probably didn't look at Python in a really long time.
Tf, who needs lambdas in python?
anyone using map, filter, reduce, or anything in itertools or functools?
List instead of array, dict instead on object (tho it also has objects)