5 ms·
I agree. Nowadays, I often provide an OO-based interface, but these objects are really just proxies to the non-OO data oriented internal system. I'm very much i
by dkersten 15y ago
I agree. Nowadays, I often provide an OO-based interface, but these objects are really just proxies to the non-OO data oriented internal system. I'm very much interested in multithreaded programming, so it often makes sense for me to dump OO in favour of more parallelism-friendly code.
I also find that functional programming is often a much more natural fit for solving a lot of problems than OO is. I find thinking in terms of streams, lists, trees, tables and higher order functions often maps much better to the data being modeled than an object hierarchy does and is often more parallelism, cache and out-of-order processing friendly than OO is. I don't really feel that OO is very suited to modern processors and certainly not to every problem we are trying to solve.