News for hackers. Stuff that matters.
Re:The Repeated Deaths of OOP (2015) by acdha on Sunday June 06, 2021 @01:14PM (#27414580)
On the other hand, when you make coffee you probably aren’t thinking about how to heat the water, measure the temperature, adjust the flow rate, etc. When you use the microwave you don’t think about cycling the magnetron to hit the power level appropriate for the settings or spin the turntable. When you drive a car, you accelerate, brake, steer, etc. without directly manipulating all of the parts & microcontrollers which respond to those control changes.

You just call coffeemaker.brew(), oven.defrost(“meat”, “500g”), or car.accelerate(). From that perspective the OOP model works pretty well.

Re:The Repeated Deaths of OOP (2015) by ratww on Sunday June 06, 2021 @02:12PM (#27415015)
Abstraction is good, but it's not a feature specific of OOP, though.

From the perspective of Procedural Programming this also works well:

brew(coffeemaker), defrost(oven, "meat", "500g"), accelerate(car).

Same for FP:

brewed(grains), defrosted(meat, time), withAcceleration(car).

Re:The Repeated Deaths of OOP (2015) by acdha on Sunday June 06, 2021 @04:11PM (#27415908)
Nobody was claiming that it was unique - if you reread the thread, I was just pointing out that the dismissal of OOP not fitting the way people thinking about the world wasn’t necessarily approaching it correctly.
Re:The Repeated Deaths of OOP (2015) by ratww on Sunday June 06, 2021 @09:49PM (#27418134)
No. Your own post your reply doesn't address any of GPs dismissals about OOP, it merely incorrectly attributes the advantages of abstraction itself ("you probably aren’t thinking about how to heat the water") to OOP.