3 ms·
Really? We did not need Rust? Here is what some of the best paid C++ Developers in the world come up with after billions of dollars invested in product developm
by belter 5y ago
Really? We did not need Rust? Here is what some of the best paid C++ Developers in the world come up with after billions of dollars invested in product development:
https://www.cvedetails.com/vulnerability-list/vendor_id-1224/product_id-15031/year-2021/opov-1/Google-Chrome.html https://www.cvedetails.com/vulnerability-list/vendor_id-1224...
https://www.cvedetails.com/vulnerability-list/vendor_id-1224/product_id-15031/year-2020/opov-1/Google-Chrome.html https://www.cvedetails.com/vulnerability-list/vendor_id-1224...
https://www.cvedetails.com/vulnerability-list/vendor_id-1224/product_id-15031/year-2019/opov-1/Google-Chrome.html https://www.cvedetails.com/vulnerability-list/vendor_id-1224...
https://www.cvedetails.com/vulnerability-list/vendor_id-1224/product_id-15031/year-2021/opec-1/Google-Chrome.html https://www.cvedetails.com/vulnerability-list/vendor_id-1224...
- mempko 5y agoYou do realize Chrome's code has a lineage that is over 24 year old, based on khtml. If you are starting a project from scratch with C++, you can avoid a lot of the pitfalls chrome's team has. Additionally Google has an arguably poor C++ coding style that is also completely out of date. A company that uses C++ more effectively is arguably Adobe, who has the great Sean Parent.
- DSingularity 5y agoCan you elaborate on the code style? So many put google c++ code style on a pedestal and force it on everyone as if it is divine.
- belter 5y agoAdobe as in Acrobat Reader? https://www.cvedetails.com/vulnerability-list/vendor_id-53/product_id-497/opec-1/Adobe-Acrobat-Reader.html https://www.cvedetails.com/vulnerability-list/vendor_id-53/p... or Adobe as in Photoshop? https://www.cvedetails.com/vulnerability-list/vendor_id-53/product_id-5467/opov-1/Adobe-Photoshop.html https://www.cvedetails.com/vulnerability-list/vendor_id-53/p...
- ygjb 5y agoUh, using Adobe as an argument in favour of C++ as a reliable programming language from a memory safety perspective is not a good argument. Just looking at the CVE count tells a story that cuts across their entire product line, and then we have the long and storied history of Flash and Acrobat vulnerabilities. Any non-trivial code base in any language will have security issues, but the argument that these security vulnerabilities are a result of using C++ poorly doesn't change the fact that C and C++ have tons of footguns and pitfalls based on both modern and legacy code.
- 5e92cb50239222b 5y agoThat's the problem with these languages (both C and C++) — it's always the user's fault. The language blows up if you accidentally miss one of the twelve thousand rules? User's fault, PEBCAK. If only the poster X was writing the software in question, these bugs never would have happened. I've seen this argument a million times.
- johnisgood 5y agoWith great power comes great responsibility. :)