←back to thread

253 points mattcollins | 1 comments | | HN request time: 0.206s | source
Show context
gigatexal ◴[] No.42190772[source]
I’m gonna buy the book but I prefer composition over OOP. I prefer to have an init that takes some params where those params are fully baked clients of whatever services I need and then the class just uses them as needed. I don’t see a lot of value in having a Python class that might have a few or more classes that it extends where all the functions from all the classes crowd up the classes namespace.

Class Foo.__init__(self, db, blob_storage, secrets_manager, …)

Instead of class Foo(DB, BlobStorer, SecretsMgr)

Etc

replies(4): >>42190800 #>>42190856 #>>42191086 #>>42193088 #
yxhuvud ◴[] No.42190800[source]
Why on earth do you put composition and OOP as opposing techniques? Composition is just one more technique in the OOP toolbox and there is nothing in OOP that mandates an inheritance based architecture.
replies(1): >>42191144 #
crabmusket ◴[] No.42191144[source]
Mainstream OOP languages (looking at you Java) have failed to make composition as convenient as inheritance.
replies(4): >>42191297 #>>42192325 #>>42192756 #>>42193209 #
1. watwut ◴[] No.42193209[source]
How is composition in Java inconvenient?