>>1
Why would you mix stupid and smart typing? For OMG OPTIMIZED? It's no point, really. And why are some people so obsessed with data types? It's better to have fewer, more useful, rich and tested data types with an extensive library of anything you'll ever need to do with them. There's no need to shoot your foot with explicit or static data types, especially when you can do all sorts of magic with dynamic data types, which adapts better to reality. Most of the times, one type and another are like a hammer and a hammer for left-handed people. And don't throw me the "error checking" bullshit because if the type of a variable is not obvious given its name it's your fault, not the type system's, and the rare cases where you could genuinely fuck up take much less time to fix than the time you take defining or dealing with types.
>>4
In the end, good design tends to make dynamic typing unnecessary.
In the end, good design tends to make static typing unnecessary. Just call the fucking function, nobody gives a shit it's a refrigerator or a lift as long as it can "Open()"! By using types you limit yourself; you degeneralize your functions and make them less useful.
>>7
No, he's talking about the retarded type hinting. For more fail, PHP didn't rip Python's object system off, but Java's, and as a result, it's full of faggotry such as type hinting. Expect a new generation of "designers" writing bullshit because of this.