> Created over 50 years ago
> Mogs low effort Zoomers
> Prefered language for most things important and low level
The cope posts about Rust are getting old.

You forgot
>needs hotfixes on a regular basis, breaking compatibility
>leaves a bunch of shit ambiguous, compilers can do whatever the fuck they want

Unix was a mistake

>>106035246 (OP)
Kernighan, Ritchie and possibly Pike are responsible for more braindead CVEs than any other people in history. They're gigantic boomer retards that had no idea what they were doing.

>>106035347
>leaves a bunch of shit ambiguous, compilers can do whatever the fuck they want
UB is a feature, retard-kun.

>>106035246 (OP)
Most important software is written in C++ actually.

>>106035246 (OP)
It seems like Latin. I've only dabbled in it and a couple other languages but it feels that others like C++/Java/C# are built on top of it.

>>106035503
>dumps everything into namespace std, with no subnamespaces

>>106035503
>C plus std::s

>>106035246 (OP)
C programmer here. 50 years ago C was very different from the C we use today. I think Pascal was a better programming language.

>>106035775
50 years ago Pascal was also a different language, retard
That's why it got left behind

>>106035246 (OP)
I'll just program in C# AND have a job instead, grandpa.

>>106035484
Explain to a programming brainlet like me what you mean.

>>106035806
>prostituting yourself for someone richer makes your habits valid and important

>>106035842
He's just crying about how millenials and zoomers can't into memory management and this is somehow Kernighan and Ritchie's fault

>>106035866
But memory management is easy? It's just malloc() and free(). Am i retarded or is it really just that easy?

>>106035886
It is, the point of some people is making it looks like the demon so they promote their garbage collected or borrow checkered languages
Anon is probably also crying about null-terminated strings

>>106035866
Just code in assembly you autistic

>>106035981
C is architecture agnostic

>>106035983
Because it's basically a tiny step up from assembly, not meant for human but for drones lol

>>106036124
Not meant for normies, zoomers and lazy people in general

>>106036179
Your shit is bugged and disgustingly full of vulnerabilities though, no wonder jeets love it

>>106036188
And what do you think your higher level languages are built on?
They just hide the real code from the spoonfed programmers

>>106036213
Well enjoy being an old mongoloid coper

>>106036241
Spouting buzzwords don't make you right

>>106036249
C is retardese, you are probably autistic

>>106035886
It's very much a human error - sometimes you forget to free() or close() or you have a branch where you try to access a previously freed pointer etc etc. C simply doesn't hold your hand which leads into a lot of negligence-based errors
Plus the types aren't actually standardized between platforms so while on most modern systems int has 32 bits, there are some where it's smaller, char isn't guaranteed to be 8 bits etc, which can lead into some memory errors (alleviated by stdint.h but that's hardly a perfect solution)
Plus the standard library contains a while lot of unsafe functions, like gets(), so you have to know which ones are ok to use and which ones are not.
Plus a whole lot of things that are allowed by the compiler without as much as a warning, but are actually undefined behavior
The language could use a lot of cleanup, but that won't happen at this point because it would mean likely breaking compatibility

>>106035886
>But memory management is easy? It's just malloc() and free(). Am i retarded or is it really just that easy?
No, that's memory management in a normal language like Pascal and PL/I. In C, you have null-terminated strings that have no way to check the length, so a program can put 1 GB of data in a buffer meant for a 10 byte string, and then that data includes malware that can exploit your computer and install ransomware on it.

>>106036213
>And what do you think your higher level languages are built on?
>They just hide the real code from the spoonfed programmers
You're wrong. Higher level languages are the real code. C is an artificial "level" of programming that shouldn't be there, just so Ctrannies can pretend to have something to do.
https://github.com/froggey/Mezzano

>>106036835
There are actually ways to check the length (yes, even safe ones)
There are ways to prevent buffer overflow exploits by simply using functions which allow you to specify exactly the number of bytes you are reading or writing (read(2) and write(2) respectively)
All C bugs are, ultimately, human error. You can argue that the language makes it very easy to fuck up, which is true, but at the end of the day it's still _your_ fuckup

>>106037196
>All C bugs are, ultimately, human error.
Because C was created by humans who designed a bad language. All those bugs in C are avoidable in good languages.

>You can argue that the language makes it very easy to fuck up, which is true, but at the end of the day it's still _your_ fuckup
Yes, because you chose to use C. You didn't have to use C, but you chose to use it on purpose, so it is your fuckup.

>>106037411
skill issue: the comment

>>106036835
Yeah, NULL terminated strings and unbounded buffers were a design mistake but it can be solved by using fat structs so the problem is not the language itself but the C mindset.

>string manipulation
>C completely implodes

>use python
>get something done about 10x faster since I don't have to write a mountain of code for one line of python

>>106035246 (OP)
No one will ever create a better programming language. C is peak programming.

>>106037519
Write a function that reverse a string in Python.

>>106037608
>import reverse_a_string
wow it was so hard

Half of the annons here are probably web shit devs. Try writting small microcontroller firmware in anything but C. I guess assembly is allways an option.

Software is not only web shit and python trash. The ignorance ITT is unbelivable.

C really is the best programming language.

>>106037411
despite C having glaring design flaws that weren't accounted for back when it was made I still use it for hobby projects due to how simple it is when you design interfaces well, also it is fairly easily translatable from pseudocode to what it already does unless you hide things behind macro slop which defeats the purpose.

>>106035246 (OP)
I unironically believe C will never die. At least not in the forseeable future.
In the year 2225, some commercial spacecraft to Saturn will have its internal operating system written in C.

You know its true.

>>106035467
Yeah I would like to imagine a world where everything is based on windows fucking server

>>106039108
having just gotten rid of windows server, I would literally an hero if I had to deal with it again.

>>106035886
https://www.youtube.com/watch?v=cNywlNWan9o

>>106039182
fireship worships c for some reason
he should write a program in it
it wont bite at worst it will segfault

>>106039182
i mean i appreciate it
and theres the c meme
but
idk
i write in c
bc its honestly easier than the rest of whats on the market ***for what i do

>>106036835
Sounds like an OS problem.

>>106038531
C is the language that won the war to become the "first sane stop to write code in above assembler". Lower level languages have basically died, and only a few survive at C's level (Fortran being the main one). Almost all nulangs are higher level in their ambition, and tend to come with more runtime overhead as a consequence; neither copies nor dereferences are free.

>>106037196
>All C bugs are, ultimately, human error.
I'd say this is correct, provided we get a complete list of anything capable of undocumented behaviour, though failing to provide said list could also be considered human error, just as a bad implementation of the compiler would be.

>>106039301
It's not an OS problem because the OS doesn't write the C standard. For it to be a C compiler, it has to have all the C brain damage, otherwise C programs won't work. If you want to use something that looks like C but works better, use JavaScript.

>>106040069
>C brain damage.
Only when you realize that absolutely every dicision made in the design of the language was geared towards performance, do you truly begin to appreciate the genius behind it's quirks.

>>106040144
Array decay and null-terminated strings are horrible for performance, unless your "performance" means job performance of hackers.

>>106040144
c is logic
and allows you to create your own interfaces
the only valid critiques of c are its antiquated libs
its function calling conventions
or its limited macros
99% of which are fixed in extended c

>>106040169
>antiquated libs
dont use em with strings

rustniggers have the borrow checker and a myriad prosneedures
c-ultists need to machine and os knowledge

id rather deal with a complex machine than with a complex framework
and so i use C

>>106040069
JS not only does away with C's linearity but its usecase is much different to C's. JavaScript is a scripting language meant to run in a web environment, if you're going to be a midwit then research beforehand.

>>106040069
The OS can read memory and detect the malware, therefore it should. Not the compiler's problem.