Re:JavaScript performance, WebAssembly, and Shared Memory in...
by johncolanduoni on Friday April 21, 2017 @03:50AM
(#14163775)
> No C++ project has been free of memory safety problems because they don't have to be.
They don't have to be free of security vulnerabilities either, but it would be very nice. What's your point?
Way to generalize there. No C++ project has been free of memory safety problems because they don't have to be. C++ is not optimized for that. Sure you can optimize for memory safety but then real hackers (not on "Hacker" News) will find something else, and then all the internet idiots will crow on about how {LANGUAGE} doesn't sufficiently protect them from {SCARY THING}.
Maybe if we stopped adding every feature under-the-sun to our browsers, memory safety problems wouldn't be so prevalent! (But we can't have that, not if there is less money to be made!)