4 ms·
I suspect “unsafe” C leads to safer server side code when combined with a few, simple libraries. One issue that seems to fly over the head of “safe” high level
by hedora 8y ago
I suspect “unsafe” C leads to safer server side code when combined with a few, simple libraries.
One issue that seems to fly over the head of “safe” high level language proponents are that you need to know what data types you are manipulating in order to write safe code.
Also, language-level isolation is much harder to implement correctly than process-level isolation (and OpenBSD has spent tons of time hardening process-level isolation).
I’d love to see a security bake off of a few mature applications built with this and random-language-de-jour.
- okket 8y ago> I suspect “unsafe” C leads to safer server side code when combined with a few, simple libraries. As many mentioned this might be true, but only if you don't have to deal with user input, strings, unicode and anything but extremely simple manual memory management. The essence is, C and similar languages like Rust are great for writing an OS or a browser, but you really, really, really do not want to write complex server side web apps in those languages. Sure, you can force your way through and if you have 30+ years of C in your head, it might even be safe. But it is not reasonable nor advisable for the general case. IMHO.
- efficax 8y agoRust brigade engage! Not sure why you're lumping Rust in with C here. Rust has automatic memory management as part of the language, without a runtime, and it has excellent libraries for dealing with Strings, unicode, and concurrency and asynchronous functions. It's a perfect language for writing a complex server side web app.
- okket 8y agoSorry, my ignorance. I've had only a brief look at Rust, it did't 'click' in my head. On a second thought, it seems much more viable than this plain C mockery. Especially with the right support e.g. https://rocket.rs https://rocket.rs