No. Learn your history and your computer science. * At the time of C's creation, there was (among others): Fortrans, Cobol, BCPL, and a set of Algols. A cursor

No. Learn your history and your computer science. * At the time of C's creation, there was (among others): Fortrans, Cobol, BCPL, and a set of Algols. A cursory check of a programming languages book or Wikipedia will verify the error. * There are a ton of C libraries. You know, if you want to go and look for them instead of expecting them to be handed to you. * Concurrency at the C layer is provided by OS/HW primitives. pthreads ain't bad, for all the whinging. * Manual memory management is very needed in systems programming (embedded programming). * A need for array bounds checking reflects slower code and lazier coder. Look at Pascal strings for the grief that can cause. * Better support for splitting- what? I can not perceive the confusion of mind that could generate this statement * "It's got curly braces, wah". Of all the complaints I have heard, this asinine complaint about (curly braces/parens) is perhaps the most empty. --- If you want a powerful systems language that isn't C or C++, try Ada. I haven't found a need for it personally, but has one zillion features. Other languages that might play in this space are Rust and D. Possibly some of the functional languages that compile out to binaries. (OCaml perhaps?) C is designed for building operating systems with, on fairly marginal resources. It is so excellent at working at that layer that no one has come up with a truly viable surviving competitor in thirty-five years. And, like any other tool, it doesn't really fit in places it wasn't designed to fit.