I thought JavaScript language equality quirks was seen as problematic not a missing feature in Python.

voidUpdate 2 hours ago | parent | next [-]

At least in javascript, it tells you if things are equal or not. In python, apparently you could answer if A is equal to B with "beans" or 17 or ['a']

	▲	hmry an hour ago \| parent [-]
		Never understood this complaint about operator overloading. In any language, a function called `isEqual` could wipe your hard drive and replace your wallpaper with a photo of a penguin. Therefore, letting programmers pick the names of their functions is bad? No, obviously naming things for least surprise is the programmer's responsibility. But when it's the symbols `==` instead of an ASCII name, it's a problem in language design? (FWIW in Javascript, being unable to override == is actually a problem when you want to use objects as Map keys)

▲

throwaway894345 an hour ago | parent | prev [-]

Python never met a footgun it didn’t need to adopt. In this case, however, it’s not equality checks, but operator overloading. I was a Python developer for a decade before switching to Go and life on this side is so much better.

	▲	data-ottawa 42 minutes ago \| parent [-]
		Operator overloading has never been an issue for me, but terminating a line with a comma creating a tuple, or white space (including new lines) between strings to concatenate have cost me days of work over the years. I understand why those exist, but they’re pure evil.