I could not state the reason that there was the change, I can say a few things I know about PHP that can give clues.
We all know, and some do not accept, that the development process of PHP is chaotic, in general performed by even good programmers, but who do not know how to create a language. Doesn’t help the fact that PHP has been created without much understanding of how a language works.
I believe that one day someone thought it would be better to have a method with a neutral name because if it renamed the class, it would save typing to change the constructor, then they decided to change the original form that was good and did not create problems for anyone for a new form that only brought a punctual and questionable advantage.
Actually it seems a very wrong reason. You should not rename your classes, this causes a lot of impact on a large system. And if you rename, the least of your problems will also be renaming the constructor within the class (you will have to rename in every application that calls this class).
Maybe it’s not so hard to change everything in the application. But if that’s true, why are you using OOP? In simple things OOP does not bring advantages, so none of this should be discussed.
PHP has other shortcomings that hamper the development of large applications that are the ones that need OOP.
It is also said that it would be in order to use the class name as a common method. I do not know what advantage this gives. I know it creates confusion because the builder will be called with the name of the class, then would have common constructor and method with the same name. Just lick.
If I’m not mistaken, you seem to have a question and or an answer talking about it! I’m not sure, but I’ll see if I can find.
– NoobSaibot