He did not ignore C, he said C++ is much easier to maintain and lets you use friendly features when it's not performance expensive. They use template as much as possible over macros, C++ debuggers, lambdas, ref counting.

I haven't watched the last 10 minutes yet, but there's no mention of C in the talk before that. The only comparison is to Assembly.

And I can't really rewatch the first half hour, but I distinctly remember he mentioned C at least two times at the begging, slightly before and during "Why C++" part. The examples of template usage also imply things not possible in C.

I watched it last night and can confirm that C was not explicitly mentioned once.

Wow, I guess I must have filled in some blanks... when he said 'other languages' or something...

Interesting, do you have link where that comment was made?

Meh. In most software test suites don't accurately portray or reflect real world workloads or results. I interpret this as 'our test suites are embarrassing'

I don't care about "real world workloads" when measure a programming language. There network latency or disk/database i/o would dominate in most cases.

I'm interested in the raw language speed/memory use in its native form, which is a good indicator of what you can do with it (e.g. "can you do number crunching? is it good for 3d rendering? can it tackle writing a fast compiler in it?" etc).