News for hackers. Stuff that matters.
Re:JavaScript performance, WebAssembly, and Shared Memory in... by pcwalton on Thursday April 20, 2017 @04:57PM (#14160800)
How is an argument that C++ is a bad foundation not relevant to the proposal that we should define the Web to be a big pile of C++?
Re:JavaScript performance, WebAssembly, and Shared Memory in... by tomc1985 on Thursday April 20, 2017 @06:30PM (#14161481)
Because a lot of comments here seem to be very skittish due to security risks due to C++'s power, yet seem to reflect zero interest in pushing one's skills to a level where avoiding those pitfalls is second-nature. Further, since people here seem to be very invested in <sarcasm>futuristic</sarcasm> technologies and <sarcasm>disruption</sarcasm> they are naturally inclined to knock C++ just because, and then rationalize it with some technical bullshit.
Re:JavaScript performance, WebAssembly, and Shared Memory in... by pcwalton on Thursday April 20, 2017 @06:40PM (#14161542)
> Because a lot of comments here seem to be very skittish due to security risks due to C++'s power, yet seem to reflect zero interest in pushing one's skills to a level where avoiding those pitfalls is second-nature.

If that is the case, then every browser engine, as well as every piece of large-scale network-facing software worked on by teams using reasonable development practices in C++ is written by unskilled programmers, since all of that software has vulnerabilities. In particular, you're saying that Google hires programmers unskilled in C++. Is that your argument?

> rationalize it with some technical bullshit.

If arguments about C++ are "technical bullshit", you should easily be able to explain why virtually no large-scale C++ project has been free of memory safety problems.

Re:JavaScript performance, WebAssembly, and Shared Memory in... by tomc1985 on Thursday April 20, 2017 @07:56PM (#14161954)
> If arguments about C++ are "technical bullshit", you should easily be able to explain why virtually no large-scale C++ project has been free of memory safety problems.

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!)

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?