4 ms·
The most typical alternative to this is that you write the hot code in an unsafe language. And your code already has dozens of dependencies on third-party modul
by dmurray 2y ago
The most typical alternative to this is that you write the hot code in an unsafe language. And your code already has dozens of dependencies on third-party modules in unsafe languages. So it's something to be aware of, sure, but it's not opening up a whole new surface of vulnerabilities.
- Retr0id 2y agoI get what you mean, but everyone already knows C is a sharp implement. It's less obvious that writing CPython bytecode has similar risks. (You can also write native python extensions in rust etc., but most people aren't doing that, yet) I'm not saying it's necessarily a reason to write off the approach, but definitely something people should be aware of.