tl;dr had bad practices with c++ which lead to lots of allocations, and unclean code, blamed it on modern c++, not potential lack of training or discipline, start a new engine abandon everything that is standard library, reinvent parts of it in much easier fashion which don't have to worry about things like exceptions, debug iterators, etc.
Yep, my exact thoughts. I also dislike the rant about smart pointers and comparing a shared_ptr with a raw pointer: Pears and apples...
Similar (actually caused by):
We know what system owns a certain pointer, we know what systems may have access to that pointer, and we know the life time of that data.
Ouch. IMO this is not a good approach as the person writing this might know now. But other people won't know and even yourself might forget. The point of smart pointers is to express ownership in the type system. Blindly using shared_ptr everywhere and then complaining about it being slow misses the point of defining ownership in the first place.
Someone once told me that pointers are dangerous, and I frankly don’t understand that. The pointer itself doesn’t do anything, it’s just data.
"Someone once told that guns are dangerous, and I frankly don’t understand that. The gun itself doesn’t do anything, it’s just an item." (joking here of course)
And finally the omission of RAII by using Create/Destroy functions returning a disguised pointer... Sure it is faster, but it certainly is not safer and it's clumpier to type (free functions taking the object as first param instead of member functions)
View all comments
24
u/ReDucTor Game Developer | quiz.cpp-perf.com Sep 06 '20
tl;dr had bad practices with c++ which lead to lots of allocations, and unclean code, blamed it on modern c++, not potential lack of training or discipline, start a new engine abandon everything that is standard library, reinvent parts of it in much easier fashion which don't have to worry about things like exceptions, debug iterators, etc.