3 ms·
I think you have to link it to more than one thing. Being able to write complex code in a performant way without being worried you've introduced another securit
by zamadatix 4y ago
I think you have to link it to more than one thing. Being able to write complex code in a performant way without being worried you've introduced another security bug in one of the most infamous subsystems for security is definitely a plus as it allows you to go after performance you might not otherwise have been able to go after in the alloted time/resources. At the same time, no two rewrites are the same and being able to look back and see how the current design performs and where it may be improved is also great insight into how to do it differently.
What I think this note bucks is the concept choosing a secure language to re-implement something in means performance overhead compared to C/C++ code that has had years or decades of work putting into it. It doesn't necessarily argue A or safe B is inherently faster, just that a safe B doesn't imply you should expect it to be safe and slower, just safe.