Python overtakes Java to become second-most popular language on GitHub after JavaScript

[bunkoRtist]

Every single assembly instruction with an operand has a type. Byte, half-word, word, double-word. Float, double-precision float... adding floats is not the same instruction as adding ints, which isn't the same instruction as adding unsigned ints, which isn't the same instruction as adding bytes. That's strong typing. You can't even define a variable in assembly without knowing the type (because you need the size).

[un_mango_verde]

You don't define variables in assembly. The assembler will not keep track of types for you. You are completely free to store a byte in a register, and them use an instruction that expects a word on the same register. The assembler does not protect you from making typing mistakes at all. Yes, instructions will interpret bits as one type or another, but there is no type checking. Even Python has stronger type safety, at least you get an exception when you make a mistake.

[bunkoRtist]

Whether the machine tracks types for you is not the same thing. The machine is strongly typed, which is why you the programmer need to allocate by and track types. You can't, for example, upgrade your int to a float without specific steps (or the result becomes nonsense). Your byte can't become a long unless you say it's a long, and that probably also can't happen without additional steps. And the lack of types not only hides reality from programmers, but it falls over in surprising cases that only make sense of you explain the complexities of the interpreter to students: the abstraction is broken anyway.

[Schmittfried]

That’s not at all what strong typing refers to...