Just discovered this talk while watching the CUFP 2014 talks.
What is interesting for the D users, are the slides related with the C++ issues that caused the decision to move away, between 03:00 and 05:30. https://www.youtube.com/watch?v=Wu8eJh6OqhI#t=181 Basically the usual points how real enterprise C++ looks like, where no one cares about "Effective C++" and similar practices. - uninitialised memory, memory leaks - no use of safer idioms like RAII, usage of deprecated idioms - low level pointer arithmetic, copy pasted in 100 places - off-by-one errors - undefined behaviours - static initialization order fiasco - race conditions - valgrid and purify could not be used everywhere Issues that D, specially in @safe blocks, takes care of. -- Paulo
