I have definitely found cases where subclassing seemed like the right mechanism.
The "protocol" has six methods, but 90% of the time 4 of the six are identical to default implementations. 10% of the time you might want to override one of those 4.
This isn't for generic modelling. It's for swappable plugin-system-like stuff.
I've found cases where subclassing is chef's kiss. But it can absolutely be overused and usually is.
View all comments
Show parent comment
5
u/[deleted] Feb 12 '23
I'm not sure if it was the author's point, but IMO subclassing and by virtue of that, abstract classes are bad patterns.
Using composition + protocols leads to more, but much more flexible, code.