Drupal is in the business of throwing the doors wide open so setting bear traps beneath the windows is wasted effort. In other words: I am not going to oppose any OOP in Drupal 8 as long as no more protected keywords are added and the current ones are removed.
Commenting on this Story is closed.
Cool Story Bro!
Protected? You mean private? Why do you have problem with protected?
As long as PHP does not support any means to add a method to a class we can't use protected, too restricted. __call, closures and anything (aside from 5.3 Reflection hackery) all does not let you add functionality to an already written class.
Protected is not evil, it avoids that messy programmers break things up. At least it will provide your IDE a good autocompletion :) Aside of that, the linked text is not that bad, we can't really oppose to it, it's a good language exercise, well passed.