> then you know where C stops working, as a language. He actually makes a really strong argument against using C right in the first two paragraphs. C is a dan

> then you know where C stops working, as a language. He actually makes a really strong argument against using C right in the first two paragraphs. C is a dangerous language. Assembly is even more dangerous. There are languages that compile to close the same speed and are systems oriented with 0 overhead. I'm truly curious, if you're working on a new project would you pick C? Or would you reach for something that's going to reduce the bugs that inevitably come from writing even 10 lines of C?