The state of OOP in PHP

  • > Don't do public and private Don't use $this and use static classes Don't overload

    You should look into functional programming.

    > and dont use interfaces

    Uhh... I guess? Interfaces are way of implementing a type system (e.g. discriminating unions) and also necessary for mocking up tests in many OOP projects.

    > Don't use namespaces

    This is just a terrible idea. Namespaces are used in almost every language to avoid collisions. Sometimes they are in the form of classes, but namespacing is hugely important.

  • Maybe you should work on yourself instead of blaming PHP OOP code that sounds just fine.

  • > the fact that it had been treated as kids language with spaghetti code for a long time

    Try using PHP with a framework.

    krapp 1388 days ago [-]

    Most of the arguments I've heard against PHP seem to amount to 'PHP is doesn't semantically resemble this other language I prefer and therefore it needs to go away.'

  • Can you explain more about what you don't like and the reasoning for it? and can you explain more about the things you are telling us to do? this other comment doesn't leave a lot of faith in your claims

  • Sounds like you might enjoy Python. It's almost as you've described.

  • What is wrong with access modifiers?