3 ms·
Some tools are just bad. I've yet to find a case where OOP was actually better than not using OOP. (e.g. a library of reusable functions and datastructures is t
by lmm 6y ago
Some tools are just bad. I've yet to find a case where OOP was actually better than not using OOP. (e.g. a library of reusable functions and datastructures is the best way to build a set of reusable components, in my experience).
- dnautics 6y agoI'm about as anti OOP as they come but I think this is uncharitable; There have been, historically, use cases where OOP was legitimately the best thing around. I think that it might be worth reconsidering on a few grounds: 1) performance bottlenecks are generally no longer CPU computation (network tends to dominate for many many things), and there is nonzero overhead to most functional operations. 2) coordination-free concurrency can in many cases often overcome computational bottlenecks, and non-OOP is far more effective for the code author in dealing with/grokking concurrency. 3) in the intervening time, functional patterns for some things (like UI) have been discovered which make fp a good fit for things that in the past were understandably the domain of OOP.