The drop is always movingYou know that saying about standing on the shoulders of giants? Drupal is standing on a huge pile of midgetsAll content management systems suck, Drupal just happens to suck less.Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]Drupal makes sandwiches happen.There is a module for that

My (current) stance on Drupal 8 and OOP

Submitted by nk on Thu, 2010-09-30 22:56

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.

Submitted by Anonymous (not verified) on Fri, 2010-10-01 07:11.

Cool Story Bro!

Submitted by Honza.Stefl (not verified) on Fri, 2010-10-01 08:46.

Protected? You mean private? Why do you have problem with protected?

Submitted by nk on Fri, 2010-10-01 09:36.

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.

Submitted by Anonymous on Tue, 2011-02-22 19:33.

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.