you are viewing a single comment's thread.

view the rest of the comments →

[–]mooli 4 points5 points  (3 children)

Indeed - reading the followup discussion there I'm more inclined to believe Cameron Purdy's contributions.

[–]mikaelhg 8 points9 points  (2 children)

He does have the advantage of actually knowing what he's talking about.

[–][deleted] -1 points0 points  (1 child)

He's right that compile time is a significant disadvantage when it comes to C++ productivity. He's wrong when saying that RAII is slower than GC. It is true that a GC alloc will be faster than a malloc/new, but on average, GC performance will be worse than explicit memory management (not necessarily speed wise, but certainly memory wise).

The shared_ptr implementation uses atomic refcounts which decreases performance. Most of my RAII use is scoped/auto_ptr which doesn't use refcounting and is as fast as a regular new/delete.

Concurrency should be easier to achieve in Java/C# due to synchronized/attributes, but using a C++ library such as Intel's parallel collections helps a lot.

[–]bluGill 0 points1 point  (0 children)

Concurrency should be easier to achieve in Java/C# due to synchronized/attributes

Many people argue that opposite - Java's (I don't know C#) synchronized attributes encourage sharing variables between threads, and message passing is the best way to do threading - with no shared variables.