44
Parse, Don’t Validate AKA Some C Safety Tips
(www.lelanthran.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Mar 2025
44 points (97.8% liked)
Programming
19301 readers
48 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
I love the argument about c having type safety with the little side-swipe at rust. "AcTuAlLy C does have type safety! You just have to jump through the following 50 hoops to get it!". I'm an outsider to both C and Rust but it's still funny.
People that say that are thinking of strong typed languages instead of type safe languages. There’s a difference. And it looks like you’re on to it.
It is pretty funny that C's type system can be described pretty differently based on the speaker's experience. The parable of the Blub language comes to mind.