this post was submitted on 18 Feb 2025
0 points (50.0% liked)

Programming

23543 readers
270 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
0
Time to make C the COBOL of this century (www.theregister.com)
submitted 9 months ago by cm0002@lemmy.world to c/programming@programming.dev
11 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] deathmetal27@lemmy.world 0 points 9 months ago (1 children)

People tend to be obsessed with bleeding edge technology. But those who truly understand know that "bleeding edge" is an anti-pattern and there's a reason it's called that: it can bleed you as well.

If it ain't broken, don't fix it.

[–] bamboo@lemm.ee -1 points 9 months ago (1 children)

If it ain't broken, don't fix it.

That’s the thing, it is broken and there is a fix desperately needed. C lacks memory safety, which is responsible for many, many security vulnerabilities. And they’re entirely avoidable.

[–] deathmetal27@lemmy.world 0 points 9 months ago (1 children)

So the solution is to take away any agency the developer may have over how their application allocates memory?