3 ms·
Nothing comes for free. I expect to have to trade something for security. It seems we have to trade speed and size. Ok, it shouldn't matter to us: this should n
by pmontra 9y ago
Nothing comes for free. I expect to have to trade something for security. It seems we have to trade speed and size. Ok, it shouldn't matter to us: this should not be developers' call. Instead it should go into a costs benefit matrix with plenty of other technical and not technical stuff. Developers will advise on their part of the matrix, marketers on their own, etc. Managers will make the decision and be held responsible for security breaches (or plauded for the lack of) as much as for every other feature of the product.
- sanxiyn 9y ago> It seems we have to trade speed and size. Why do you think so?
- wongarsu 9y agoIn principle things can come for free. Sometimes something new is strictly better. I am fairly confident that GCC outperforms early C compilers in every relevant metric (in theory GCC is ofc vastly more expensive because of decades of labor invested in it, but I don't pay that investment). Right now Rust is slower than C (though not always slower than C++), produces bigger binaries, and compiles slower. But more safety required a more expressive language, and a more expressive language contains more information for code generation and optimizer. It's certainly conceivable that in a few years the Rust compiler might generate faster code than C compilers.
- roca 9y agoUnfortunately in the real world people are shortsighted and focus on immediate concerns like development velocity and performance at the expense of long-term concerns like latent vulnerabilities. Managers and developers who make these decisions today aren't going to still accountable when a critical bug is discovered in deployed code ten years later.