As for the specific examples which he brings up, those also get the specific goal stated as to why C++ has that strange condition.
Essentially, I don't know what you are complaining about.
I just loaded it up again and went to 43:40 and yes, that's a good conclusion: the thing D doesn't need is an overly-broad list of design principles. I do think he could have come to that conclusion a lot quicker and with a LOT fewer examples.
I also must confess, I didn't watch the video. I was there, so there is a good chance the presentation doesn't translate well to video in terms of speed of content.