41
submitted 2 months ago by [email protected] to c/[email protected]

A shitpost about languages that generate CVEs

you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 7 points 2 months ago* (last edited 2 months ago)

Right, those devs with 20+ years C experience don't know shit about the language and are just lazy. They don't want to catch up with the times and write safe C. It's me, the dude with 5 years of university experience who will set it straight. Look at my hello world program, not a single line of vulnerable code.

Anti Commercial-AI license

[-] [email protected] 4 points 2 months ago

This is not completely wrong, though

[-] [email protected] 1 points 2 months ago* (last edited 2 months ago)

Yeah, for sure. Human error is involved in C and inertia too. New coding practices and libraries aren't used, tests aren't written, code quality sucks (variable names in C are notoriously cryptic), there's little documentation, many things are rewritten (seems like everybody has rewritten memory allocation at least once), one's casual void * is another's absolute nono, and so on.

C just makes it really easy to make mistakes.

Anti Commercial-AI license

[-] [email protected] 2 points 2 months ago

It has nothing to do with knowing the language and everything to do with what's outside of the language. C hasn't resembled CPUs for decades and can't be reasonably retrofitted for safety.

this post was submitted on 03 Jul 2024
41 points (79.7% liked)

Programmer Humor

19197 readers
1153 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS