News for hackers. Stuff that matters.
Re:The Repeated Deaths of OOP (2015) by bookofsand on Sunday June 06, 2021 @09:35AM (#27413043)
For yet another definition, OO is about encapsulated polymorphic interfaces. Which raises a communication difficulty: encapsulated polymorphic interfaces are very useful in some of the cases (ADTs, modules), and a misfeature for the other cases (data modeling). I have yet to see a conversation, especially an internet conversation, where participants reach a rough consensus on the contextualized upsides / downsides of a given concept. It's either 100% heaven or 100% hell.
Re:The Repeated Deaths of OOP (2015) by ncmncm on Monday June 07, 2021 @12:29PM (#27424468)
Use it where it's useful, use something else otherwise.

It doesn't need much discussion.

If your language forces you to use mechanisms and organization inappropriate to the problem, the solution will be ugly and awkward. In that case a better language, or more usually a better job, is in order. The requirements might dictate the language, but they don't typically dictate you being the one to do it.

Re:The Repeated Deaths of OOP (2015) by jasperry on Sunday June 06, 2021 @11:12AM (#27413728)
Do you have any references with detailed analysis of this issue? How much one should emphasize concrete data types vs. interfaces seems like a key consideration in language design.