3 ms·
I really enjoy reading these war stories, even though this sounds like a super difficult time for the author. On a technical note though, aren't these kinds of
by matt2000 8y ago
I really enjoy reading these war stories, even though this sounds like a super difficult time for the author. On a technical note though, aren't these kinds of breaches a powerful reason to use memory safe languages? I know performance used to be a major driving factor, but I doubt that's the case anymore. Even then, does it seem reasonable to say "I'm risking it all for a 20% performance gain"?
Admittedly, this isn't the kind of stuff I normally write, so I might be missing something. But since the ramifications of these memory leaks are so severe, I would think the industry would be adapting.
- jgrahamc 8y agoYes. And tomorrow's installment of this series of posts begins: After Cloudbleed, lots of things changed. We started to move away from memory-unsafe languages like C and C++ (there’s a lot more Go and Rust now).
- matt2000 8y agoOh! Well there's my answer then, looking forward to reading that.
- matthewaveryusa 8y agoThe biggest problem leaving C/C++ is GC jitter. GCed languages go through massive hoops to minimize it but it's dtill there and in some workloads the jitter is simply unacceptable