"No way to prevent this" say users of only language where this regularly happens - 07/01/2024
"No way to prevent this" say users of only language where this regularly happens - 07/01/2024
Xe Iaso's personal website.
A shitpost about languages that generate CVEs
You're viewing a single thread.
The "C is bad trope" is getting way too old. I'm surprised the author didn't plug Rust.
the only programming language in the world where these vulnerabilities regularly happen
Maybe because it's one of the most widely used languages in the world...
22 13 ReplyThe trope will be "old" once the mainstream view is no longer that C-style memory management is "good enough".
That said, this particular vulnerability was primarily due to how signals work, which I understand to be kind of unavoidably terrible in any language.
27 0 ReplyA better language wouldn't have any need to use POSIX signals in this way.
5 1 ReplyI'm not totally clear on why signals are used here in the first place. Arguably most C code doesn't "need" to use signals in complex ways, either.
9 0 Reply
Well, one of the most widely used that allows to do low-level stuff. The most widely used one is by far JavaScript but good luck making an OS or a device driver with it
12 1 ReplyI'm sure there are projects covering those areas written in JavaScript.
2 1 ReplyJust because you can doesn’t mean you should and i hope that is not a thing
6 0 ReplyOh gawd. That would be so horrible! Is there a project o compile JavaScript to bytecode? With like LLVM? There must be, but I haven't heard of it. I shouldn't even say anything because I will be better off pretending it doesn't exist.
4 0 ReplyJust bundle a JavaScript interpreter with the JavaScript code. No need to compile JavaScript.
1 0 Reply