> It only has one group of functions to allocate memory, and neither of them can be configured Seriously, have you done any non-trivial C programming? Because

> It only has one group of functions to allocate memory, and neither of them can be configured Seriously, have you done any non-trivial C programming? Because those are blatant falsehoods. You must be talking about uni level introduction to C programming, using malloc/free and thinking that's how you "allocate". > You are again confused... there weren't such codebases in C because C is bad for this. It's not because nobody wanted it. Highly concurrent codebases existed in Erlang since forever, for example. Just one example I know, take the Linux kernel which had a good amount of SMP support way before C11. I believe they still haven't switched over to the C11 memory model. > The point is not that they cannot run in parallel... The point is that C doesn't give you tools to program them to run in parallel. How come then, that my computer is running so many things, many of them written in C, in parallel?