3 ms·
The issue is that we don't need OOP anymore--people forget that OOP had its heyday when memory and performance were much smaller. Passing a big list around, do
by bsder 7y ago
The issue is that we don't need OOP anymore--people forget that OOP had its heyday when memory and performance were much smaller.
Passing a big list around, doing something to it, and passing back the entire list is no big deal today.
It's a much bigger deal if you have to do some weird decompression/insert because your main memory isn't large enough to hold the whole thing uncompressed. You need a "gatekeeper" to the single thing--and you may need coordination between the "gatekeepers" so they don't decompress simultaneously.
Or, you build a huge hierarchy of objects into a GUI because you don't have the memory to store the rendering state of each one so you want to be able to look it up from it's parent.
Oh, and you only have one thread.
In an era of gigantic memory and dozens of threads, the "advantages" of OOP simply don't make sense.
- ncmncm 7y agoThis argument does not make sense. The more data you have, the more structure you need to help organize it.