Programming Circlejerk

161 readers

20 users here now

Community to talk about enlightened programming takes

Rules:

read and follow the programming.dev code of conduct
no flamewars
mark your unjerks
only programming related content allowed
link to the original source
do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.

founded 2 months ago

MODERATORS

[email protected]

When I found out even Rust needed the clib, it was like seeing an iron-clad fortress only to look closer and see it was being held up by sticks, ducktape, and prayers. (github.com)

submitted 5 days ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

Every programming problem I have, when I track it down to it's source, seems to originate with C/C++. It wasn't till a few years ago that I realized how seriously everything I do somehow, some way, has C/C++ as a foundation. Basically every zero-day exploit in my cyber security class is because of something stupid in C/C++. And it goes well beyond security, the more I dive into C++ the more terrible stuff I find. When I found out even Rust needed the clib, it was like seeing an iron-clad fortress only to look closer and see it was being held up by sticks, ducktape, and prayers.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 14 points 5 days ago (1 children)

Thank god assembly is memory safe!!

[–] [email protected] -1 points 5 days ago

It is indeed when paired with an optimizing assembler, a sophisticated static analysis tool in its own right. And just like Rust, you have greybeards hating on such provided safety because "meh it's not close to the hardware anymore", like that old man Mel.