"Have you ever used the STL? I did for about 6 months professionally, and I'm glad that I could go back to C and Python. More seriously, object orientation in C++ doesn't come for free. Aside from the pain of the syntax of using C++ templates (and difficult to parse error messages), all of that object orientation hides the complexity of method dispatch in what are known as vtables. If your system has to call them to dispatch, you are wasting time in that processing when you could be doing something else."
This fragment made me WTF, so either I missed something in the C++ development of last few years, or...
a) How can you make standard-OOP-like method dispatch faster than vtables?
b) Since when STL uses so much of virtual functions anyway? Last time I checked, it avoided any kind of polymorphism at all, for speed reasons. (and it doesn't really need to use much; C++ templates are nice tools that can make a pointer to function and a function object work in the same place just because you can stick "()" to the right of the passed parameter and it will compile, no run-time work needed).
c) (it seems to be implied, though not explicitly stated). Going faster than STL... in Python?
This fragment made me WTF, so either I missed something in the C++ development of last few years, or...
a) How can you make standard-OOP-like method dispatch faster than vtables?
b) Since when STL uses so much of virtual functions anyway? Last time I checked, it avoided any kind of polymorphism at all, for speed reasons. (and it doesn't really need to use much; C++ templates are nice tools that can make a pointer to function and a function object work in the same place just because you can stick "()" to the right of the passed parameter and it will compile, no run-time work needed).
c) (it seems to be implied, though not explicitly stated). Going faster than STL... in Python?