▲ | IshKebab 5 days ago | ||||||||||||||||||||||
That feels like a very binary view of security. There are certainly cases where something like RLBox takes you from "horrific anything-goes C security" to "probably fine". Image parsing for example, which is a common source of vulnerabilities. So the question of performance is still relevant, even if RLBox's security properties are less tight. | |||||||||||||||||||||||
▲ | pizlonator 5 days ago | parent [-] | ||||||||||||||||||||||
I think you're trying to compare RLBox and Fil-C because you view them both as "add more security". I get it and that's not entirely unfair, but... They're just way too different. RLBox is a containerization technology. Fil-C is a memory safety technology. Like, there's a world where you would use both of them stacked on top of one another, because Fil-C does memory safety without containerizing while RLBox does containerization without memory safety. | |||||||||||||||||||||||
|