First of all, his classification of people into groups is not precise. It seems that people who say "I don't know the right answer yet" end up in the Moderates group and that's labeled "insanity". But that's the safest way to proceed, especially if you're building something to last, like a programming language.
Later, he goes to argue about a type system. His argument is that people are able to write big systems without a static type system. For some reason, he classifies them as the Radicals (=they are right) and the proponents a strong type system as the Reactionaries (=they are wrong). But the point here should not only writing big systems, but also maintaining them. You can write huge apps in assembler, but that's almost write-only code. Earlier in the talk, Crockford was proposing fixing the + operator for reasons including performance. But strongly typed languages' compilers can generate optimal code for string concatenation and number adding while using the same operator thanks to the type information. How can he miss that fact is beyond me. So maybe the strong type system is worth the extra effort?
His last point is about classes and that a class-free approach is better. He states that doing entity classification correctly is hard and we usually do it at the beginning of the project. But that's just false. Well, at least it's not the right way to do it. The domain model that is expressed in the classes should evolve as we get better understanding of the problem that we are trying to solve. And then the requirements change. But that's not really an issue if you have the right tools to refactor (change the implementation without changing the behaviour so that the code is easier to understand and modify). And then he goes to propose his way of doing OOP in JS. But the thing is that it doesn't really differ much from the classical way. The difference is that with classes, the definition is declarative (you declare the methods) and he's proposing an imperative way (you put the methods into the object). I'd say the declarative way is easier to analyze for both humans and computers.
Surely, object-oriented programming is not a silver bullet, but neither is functional programming, especially when the business logic gets really complex or you really need to have some state.