Quote:
And 70% (or thereabouts) of all Python programs must indicate in the implementation language in the program name. (Even Visual Basic programmers don't feel a need to give their programs names starting with "vb"!)
That's just petty.
Quote:
ARM ABI and dotNet leaves me with a much better gut feeling. They encourage me to use the language that is best suited for the task. Python does not. It more or less demands that I use Python, whether suitable or not. It takes away my freedom. That is probably on top of the list. The two other points come in second and third.
Using an ABI would make sense if Python was a low-level system language. It's not, and was probably never intended to be one; the language itself is written in C (See CPython). It's meant to be an abstraction-layer language, and if C can use an ABI, it wouldn't take very much work to abstract it in Python. I like Python because it's a simple language that allows me to write up a proof of concept with very little impedance between the idea and the application in itself. If I need OOP, I can use it, but I'm not required to. Type checking is an option, and what's more free than being allowed to choose? Have I made embarrassing messes with Python? More than I'd like to admit, but every time I did, I learned that I wasn't thinking in Python, but thinking in X-Language, and *translating* it into Python. Since I don't work in Python on a daily basis, thinking in Python (TIP) doesn't come as easily for me as it would otherwise. Nonetheless, when I'm in a TIP-state of mind, the code I produce is leagues ahead of what I produced with the thinking-in-X-then-translation method.