9 ms·

It turned when you decided to pretend that you thought all OOP meant smalltalk style OOP and when you chose to act like you were talking about relations in term

It turned when you decided to pretend that you thought all OOP meant smalltalk style OOP and when you chose to act like you were talking about relations in terms of sets and not sql. You pretended you didn't know the context when it's fairly obvious what the context is. You are playing a part. You don't love to learn new things, that is not your objective here, your objective is to troll. This conversation is over.

randomdata 4y ago
OOP in the discussion was undefined prior to me choosing a definition. Smalltalk-style OOP is quite significant to the topic as what are probably the only respected ORM toolkits (CoreData, ActiveRecord) lean heavily on the facilities provided by what you call the Smalltalk-style OOP paradigm. I might even go as far as to say that the active record pattern is unusable without Smalltalk-style OOP. Other languages have certainly tried, but it gets janky really quickly. Now, it's okay if OOP means something different to you. Words are just tools to help with communication, not some source of pride or identity. That is why definitions were laid out to ensure that we weren't just talking past each other. Despite this making you believe I am young, in my 30 years of development experience I've learned that you can't assume everyone uses the same definition. In software, it is actually quite rare to find any common definition across any sizeable group of developers. There is no logical reason to leave a discussion because what OOP meant to me differs from what OOP meant to you. The OOP talk that was present early in this thread didn't even carry into the remainder of the conversation about ORM, so it is moot anyway. The reality is that this conversation has reached a dead end because there is nothing left to talk about. We've established that ORM and query building are different operations, which rounds out the entire topic of the thread, and that's that.
- fckgnad 4y ago
  >There is no logical reason to leave a discussion because what OOP meant to me differs from what OOP meant to you there is reason to do so if you're trolling.

randomdata 4y ago

OOP in the discussion was undefined prior to me choosing a definition. Smalltalk-style OOP is quite significant to the topic as what are probably the only respected ORM toolkits (CoreData, ActiveRecord) lean heavily on the facilities provided by what you call the Smalltalk-style OOP paradigm. I might even go as far as to say that the active record pattern is unusable without Smalltalk-style OOP. Other languages have certainly tried, but it gets janky really quickly. Now, it's okay if OOP means something different to you. Words are just tools to help with communication, not some source of pride or identity. That is why definitions were laid out to ensure that we weren't just talking past each other. Despite this making you believe I am young, in my 30 years of development experience I've learned that you can't assume everyone uses the same definition. In software, it is actually quite rare to find any common definition across any sizeable group of developers. There is no logical reason to leave a discussion because what OOP meant to me differs from what OOP meant to you. The OOP talk that was present early in this thread didn't even carry into the remainder of the conversation about ORM, so it is moot anyway. The reality is that this conversation has reached a dead end because there is nothing left to talk about. We've established that ORM and query building are different operations, which rounds out the entire topic of the thread, and that's that.

fckgnad 4y ago
>There is no logical reason to leave a discussion because what OOP meant to me differs from what OOP meant to you there is reason to do so if you're trolling.