Satan is the father of lies

These C liars constantly claim that the work of other people came from C and Bell Labs hackers. Who would do that other than Satan and his servants?

They are so deluded by Satan that they believe the idea of variables and ASCII text came from C.

Okay, what y'all youngins need to understand is what programming looked like before C, and what it looked like with C.

What if, rather than manually typing in memory addresses, you could store stuff in variables that the rest of the program can access BY ENGLISH NAME? Or, when you need to, store memory addresses in variables, which you could still access by name? What if you automated all this, so the program itself allocated, read, and wrote memory addresses to the variables, so no programmer would ever need to do it themselves?

THIS is the level we're working at, OP. For some newage twirp to say it's a "fundamentally flawed language and has many errors" is just mentally painful. By errors he means "It doesn't do this thing we have space to run now, it not doing something that other things do is a FLAW and an ERROR"
We went from "Manually type in the address of the thing you want, or maybe offset stuff from an address if you really want, either way you're keeping a spreadsheet full of hex codes on your desk if you like it or not" to "Lol here it all is, named and everything, no need to know the address, you can simply copy the address of a variable to another variable and use the second to access the first, if something out of scope wants direct access to the first, just give it the second and it can do what the fuck it wants, go wild with math if you like but don't be a twat and TRY to keep track of where everything is"
Do you even begin to understand how much of a DREAM this shit was to programmers? It's all these halfwit newbies that think the compiler should keep everything safe for them no matter what that look at C and go "Now, this language so utterly pure and without clutter, it's FUNDAMENTALLY FLAWED and HAS MANY ERRORS because IT'S NOT FULL OF SHIT THAT DOES EVERYTHING FOR ME, IT DOESN'T GET IN THE WAY, IT DOESN'T STOP ME FROM DOING WHAT I WANT, IT EXPECTS ME TO KNOW WHAT I'M DOING, IT'S SO GARBAGE BECAUSE I'M TO FUCKING DUMB TO FOLLOW THE SIMPLEST RULEBOOK IN PROGRAMMING"

YES YOU HAVE TO KEEP A VAGUE IDEA OF HOW YOUR MEMORY WORKS, BUT C DOES SO BLOODY MUCH FOR YOU THAT ANYTHING MORE IT LITERALLY "BABBIE FIRST DRAG AND DROP HOCKEY GAME"
IT'S NOT EVEN MANAGING MEMORY, IT'S SITTING IN YOUR COMFY OFFICE TELLING THE PR GUY TO GET RID OF DEPARTMENTS YOU DON'T NEED ANYMORE, AND ADDRESSING EMPLOYEES BY THEIR BADGE NUMBER, NOT THEIR NAME, GENDER, WHAT OR WHO THEY ARE, JUST A SIMPLE NUMBER, AND PEOPLE STILL MANAGE TO SCREW IT ALL UP AND SAY "IT'S TOO HARD"

>>19
Logic errors will always exist, but a crippled language such as C will push the burden of thinking about many more classes of error on the programmer when it is not necessary to do so.
Why do you think virtually all new desktop programs are written on top of a browser? It's because all the existing GUI APIs are crippled by being written in bad languages like C and C++, and it takes an enormous amount of code and effort to get anywhere close to what you could already do with a few lines in the 70s with Smalltalk.
A programming language with a non-memory-safe superset would have been a million times better, because it would have relegated the unsafe sections of a system to its edges where they belong, and let the average programmer work on the infrastructure that we base all of our programming on faster and using more sensible designs, not crippled by the mindset that comes with using a crippled language.