It's about time to question whether writing secure software is possible in C at all.https://twitter.com/kayseesee/status/927923337543655424 …
Fucking language should handle them gracefully. Programmers are human. Humans make mistakes. No amount of training will ever prevent this.
-
-
yep and who builds them? im trying not to go on lang x mainly because i like c, but.... i also like speed and when i buy something with 16gb of mem i expecting to have 80% of that for my stuff....
-
"Sure it's vulnerable, but look how fast it is!" No seriously, have a look at Rust. Speed, memory efficiency and safety do not contradict each other.
-
i will :)
End of conversation
New conversation -
-
-
theirs no silver bullet... in the end we all need to use our brains and collective knowledge and keep our shit updated
-
There is a silver bullet for memory corruption, and it's called memory safe languages. Just giving up on safety at all is ridiculous.
-
i worked with java and ppl used to say that about java ... truth is in the end before i left dev my job was to fix mem issues on java apps... they not likely to give you rce but most of the time will take it down.. and you get questions like "why do i need to close a file"
End of conversation
New conversation -
-
-
if we take llvm and that new stuff... is a memory eating best.. complex and generic takes evething away and in the end you still have bugs.. abstraction is realy hard to get right and most of the time will take more resouces than it should..
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.