Re:Rust in 2018: easier to use
by civility on Sunday January 14, 2018 @06:22AM
(#16143794)
Heh, so does yours. I can say this without even knowing what language you use to write your software, much less looking at it... All software has bugs, and most of those are security vulnerabilities waiting to happen.
[ Parent
| on HN ]
Re:Rust in 2018: easier to use
by raverbashing on Sunday January 14, 2018 @09:42AM
(#16144417)
Of course. Code is hard.
Using a safer language makes it easier and less prone to out-of-bounds memory accesses.
By using C/C++ you're choosing to make a hard problem harder.
Re:Rust in 2018: easier to use
by banachtarski on Monday January 15, 2018 @04:10AM
(#16149431)
And slower or impractical even for some things. Maybe we should write a real-time media codec in python 'cause security. I don't understand why you, like the OP, make these sweeping generalizations as though all of engineering is black and white. Sometimes, I reach for a higher abstraction, sometimes not. It depends on the problem domain.
Oh and btw, "out of bounds memory accesses" are not the primary source of security vulnerabilities at all. In fact, such out of bounds access is more likely to just make your program crash (which is a good thing).
Re:Rust in 2018: easier to use
by duneroadrunner on Sunday January 14, 2018 @03:08PM
(#16146076)
C++ does have a practical, memory-safe subset[1]. Recommended for anyone writing internet facing C++ code.
[1] shameless plug: https://github.com/duneroadrunner/SaferCPlusPlus