I just hat a look at the code of PHP Unit and must say this is one of the many examples where a key library uses the worst OOP patterns that lead to a complex nightmare of data ping-pong. Is there any movement that with a name against this sort of overdona OOP? Have seen this on many projects and there is so much wrong about it that I dont know where to start. It seems like OOP in PHP has a tendency to overcompensate the fact that it had been treated as kids language with spaghetti code for a long time.
My proposal for better code:
Don't do public and private
Don't use $this and use static classes
Don't overload and dont use interfaces
Don't do namespaces
Might sound a bit backwards but I am really sick of seeing this mindless OOP shit all over the place ...
My proposal for better code: Don't do public and private Don't use $this and use static classes Don't overload and dont use interfaces Don't do namespaces
Might sound a bit backwards but I am really sick of seeing this mindless OOP shit all over the place ...