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, catch/except 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.
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.
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.
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…
So not only did they decide to randomly include Hebrew in their language, because I guess they were feeling kabbalistic, but they got the Hebrew wrong. In what way does any of that increase usability or even make them look competent?
It reminds me of the INTERCAL manual, which was a joke:
This precedence (or lack thereof) may be overruled by grouping expressions between pairs of sparks (’) or
rabbit-ears (").
Yeah, that’s not actually a good reason though, unless you’re developing a Hebrew programming language for Hebrew speakers. I made a bit of a joke about it, yes.
But python lists are not like the base arrays in other languages. They function more like List<> or vector (C++ had to be special) and are named appropriately.
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.
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.
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
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.
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, catch/except 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.
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”.
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
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…
You could even choose the name this.
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
matchisn’t just equivalent toswitchthough, so in this case it actually makes sense to call it something different.This is very true. Match statements are much more powerful that switch statements in any other language.
For instance:
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.
PHP weirdness and inconsintencies never fail to amaze me.
On the bright side, I found my first StackOverflow answer that would fit exactly the same on Linguistic Stack Exchange.
https://stackoverflow.com/a/59259755
Absolutely cursed, lol.
So not only did they decide to randomly include Hebrew in their language, because I guess they were feeling kabbalistic, but they got the Hebrew wrong. In what way does any of that increase usability or even make them look competent?
It reminds me of the INTERCAL manual, which was a joke:
… or because the developers were Israeli: https://en.wikipedia.org/wiki/Zend/_(company)#History
Yeah, that’s not actually a good reason though, unless you’re developing a Hebrew programming language for Hebrew speakers. I made a bit of a joke about it, yes.
List and Array terminology also bothers me … Why not just call it an array?
But python lists are not like the base arrays in other languages. They function more like
List<>orvector(C++ had to be special) and are named appropriately.Ahh thank you for that information! In all seriousness, I appreciate you correcting my ignorance.
List instead of array, dict instead on object (tho it also has objects)
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.
Maybe I’m missing something, but:
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.
i mean tbf match case was only added in 3.10
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
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
Tf, who needs lambdas in python?
anyone using map, filter, reduce, or anything in itertools or functools?
deleted by creator