Thursday, February 7, 2008

Selfdoubt

Here I am, trying to implement models and fields (I think I'm getting some progress), and I think I have found a feature deficiency in object oriented programming. I'm trying to do something, and I can't, because OO doesn't allow me. No, it's not PHP, but the OO paradigm itself that's limiting me.

When asking around about this, I'm getting more and more the impression that I can't "write in OO". Ok, that's not very far from the truth and I accept that argument - my previous projects really haven't required extensive use of objects. I'm going out on a limb here, but is it possible that because a way of thinking prevents me doing something, that way of thinking is not perfect?

Today, it seems, you can't call yourself a programmer, if you can't grasp the correct philosophy of Object Oriented Programming. I've never grasped the correct philosophy of Object Oriented Programming, because plain functions have served me fine in the past, so I must not be a programmer. But I'll be damned if I get ridiculed just because I want to use the class name of a subclass as a value for further processing. "No, you can't do that! You must do a method in the subclass that returns __CLASS__."

Fuck that. OOP makes some things just unnecessarily complicated.

No comments: