News for hackers. Stuff that matters.

A comment on JavaScript performance, WebAssembly, and Shared Memory in Microsoft Edge. Parent comment

Re:JavaScript performance, WebAssembly, and Shared Memory in... by flatline on Friday April 21, 2017 @12:28AM (#14163099)
There's nothing wrong with modern C++, I think it can give any other language a run for its money in this space. If you are talking about a complete re-write, I don't think you can fairly overlook it. RAII + smart pointers eliminate the most pernicious memory management issues. The STL has grown to parity with other modern platforms. Even without a rewrite, given enough time and effort, that crappy old Konquerer codebase may even turn out to look reasonably good.

I would not, however, wish it to be the only thing available.

[ Parent | on HN ]
Re:JavaScript performance, WebAssembly, and Shared Memory in... by dragonwriter on Friday April 21, 2017 @12:43AM (#14163141)
> There's nothing wrong with modern C++

The fact that it's a set of practices to avoid the deathtraps within a language which itself has plenty of problems left lying around is, arguably, the problem with modern C++.

[ Parent | on HN ]
Re:JavaScript performance, WebAssembly, and Shared Memory in... by flatline on Friday April 21, 2017 @01:27AM (#14163288)
Yes, that is the problem. It's also what allows you to drag that 20 year old mess forward into the 21st century. It compiles to virtually any platform with a number of compilers. Trade offs...
[ Parent | on HN ]
Re:JavaScript performance, WebAssembly, and Shared Memory in... by johncolanduoni on Friday April 21, 2017 @03:52AM (#14163782)
What platform needs/wants a web browser that isn't covered by an LLVM target?
[ Parent | on HN ]
Re:JavaScript performance, WebAssembly, and Shared Memory in... by pcwalton on Friday April 21, 2017 @10:37AM (#14165956)
> RAII + smart pointers eliminate the most pernicious memory management issues.

No, they don't. Browsers have been using RAII and smart pointers for years and years. The memory management-related vulnerabilities keep happening.

The biggest problem tends to be use-after-free, which smart pointers do absolutely nothing to mitigate.

[ Parent | on HN ]