Post #4022181

I still gotta do my Smalltalk writeup at some point (not right now - I have about 27 minutes to cram progress on a music video before I have a social obligation), but the not-obviously-terrible premise that early OOP was exploring was the premise of nesting computers inside of computers, just in a lighter way than VMs. Turns out, if you pull that thread, you find out that computers *can* be nested, they just don't really like to, the dissonance offloads into cognitive overhead for the author, and this can make it hard to manage performance problems. Meanwhile, data nests inside data, and execution nests inside execution, happy as a pair of clams. That's a nice property you preserve with systemic thinking/data-oriented design/system-oriented design, which are all either extremely similar terms with microscopic nuances in meaning, or completely interchangeable. Debate in the comments or whatever.