>These groups of programmers ... were horribly uninformed about basic computer science Reading his previous post about Python 3, I think this description is mo

>These groups of programmers ... were horribly uninformed about basic computer science Reading his previous post about Python 3, I think this description is more fitting to him. His last post discusses such topics as "statically typed strings" which are "not as statically compiled as they could be". You don't need to be an expert to understand the differences between static/dynamic and strong/weak typing (plus he uses both of these terms to mean two different things in the article). Remember that this is written by someone with apparently enough expertise to write a book about C. He states that Python 3 is not Turing complete because a virtual machine for Python 3 bytecode cannot run Python 2 bytecode (but makes no such argument when he mentions other languages that clearly don't run Python 3 bytecode). Yet he constantly references phrases like "it's all in the math!" or "it's basic computer science." All this article amounts to is a bunch of name-calling and damage control for the criticism he got for mistakes in his last article. That he feels so defensive about mistakes to go and bash the people trying to help him makes me much less likely to ever recommend his books. Look back at the "Learn Python the Wrong Way" damage control article, in which he "called out" a programmer who he had (secretly) offered to pay to help make corrections because that guy didn't have time to help out. Rather than going with the corrections from the original article, he attempted to publicly shame the other guy (repeatedly calling him a "beginner programmer" and claiming he has no skills, not to mention lying about his motives). If /r/programming was wrong in unlisting his book because of the contents of it, they were certainly correct in stopping their support of someone this toxic.