I’d be very worried about a security issue with the unsafe C++ code.
You really have to run this kind of complex parsing in a disposable containerized environment to do it safely. Or do everything carefully and in a memory safe language.
You really have to run this kind of complex parsing in a disposable containerized environment to do it safely. Or do everything carefully and in a memory safe language.
See the persistent, years-long trend where mobile devices and game consoles get exploited via some combination of libtiff and libpng.
However, there isn't much choice. Performance is very important in image processing, so much that many libraries contain hand-written assembly. In the article, it says that 90% of processing power is dedicated to it. Using a safer language in a safe way could completely kill performance and significantly increase the costs.
I also recommended a mitigation strategy for unsafe code. Complaining that security is too hard is the reason for the situation we find ourselves in as an industry.
seems to vary wildly. for some, it's not that expensive.
How much indeed ? What was the last time ? Ah, yes, Equifax. What happened ? Nothing.
if i was a betting person, i'd wager that it may see somewhat like "rewrite it in rust" cargo culting.
It's the entire reason python is generally fast enough, anything that's slow generally uses a C lib under the hood anyway.
Also, your life must be very stressful.