> The ontological problem of "does the knife cut the cucumber" or "does the cucumber get cut with the knife" seems serious. Kinda both! The knife (aka: the "Cu

> The ontological problem of "does the knife cut the cucumber" or "does the cucumber get cut with the knife" seems serious. Kinda both! The knife (aka: the "Cutter") can perform a "Cut" action on any object (aka: the "Cutable"), but the Cutable objects have to receive the Cut action and determine if the Cutter has enough "Cutter.Strength" to Cut the Cutable. I think the failure of OOP is applying it to things that aren't appropriate or creating a Factory pattern that causes over-abstraction. OOP in itself isn't bad, much like PHP or Windows has their place even though they get shit on all the time, but the lack of care applying OOP (or any other pattern or architecture) is the bad part.