bitch about it? C is complete crap that's why, except for legacy work, or forced to deal with a env. with old compiler support only, why would anyone in there right mind use C?
c++14/17/20 rules the day (even C++11 is great, but given where we are now in time c++14/17 rocks), C++ is a super-set of C (in practice). Doing C now is like driving a old model T with
wooden wheels, certifiably bat shit crazy. Golang was dev'd apparently to give C++ programmers a better place, they didn't come, but c++11/14/17/20 rocks and makes golang a complete fail,
but when golang was developed/invented C++ was in its pre- c++11 very sad state. It's reborn, its basically a new language , a non-jvm c# in a way, the unique_ptr, smart_ptr totally rock, iterators,
lambda, and all OOP goodness, move-semantics, whats not to absolutely love (ok template programming especially SFINAE is not to love, but :) ).
I hope and pray when you say "C" you really mean c++14/17? C is _dead_, done and dusted, gone, kaput, finished! absolutely no point in ever using it
(except for rare cases i stated at start), and of course C++ is super set of C, so you got your full C naked pointers and pain
and memory leaks if you really want them still! :) C language % popularity on language ranking sites is primarily C use for historic, legacy, etc. I mean like 99.9% of us C++ programmers _are_ a C programmer too, so C gets that tally, but that doesn't mean you are actually going to work in that subset of C++ unless someone is holding a gun at your head, or pulling up your fingernails.
Having said all that, as a good C++ programmer, you do learn C fully as a byproduct, but that doesn't mean you stay stuck at the "just C" level.
-tl