| 5 | | As someone you has learned PHP practices mostly from WordPress, I can say that the way I do OOP is largely based on what WordPress does. If WordPress improves, so will I, and many others will too. However, there is a difference between growing my knowledge of OOP alongside WordPress and a newbie trying to break into WordPress development after the fact. I think if it *seems* too complex, it may discourage some people from getting in (not necessarily a bad thing, mind you). It took both me and @welcher some time to wrap our minds around it, but I think in some ways the end product will actually be simpler than what is was before, once a dev cracks the entry barrier. And, because backward compatibility will be maintained, newbies can continue to use the old approach until they better understand the new underlying API. |
| | 5 | As someone who has learned PHP practices mostly from WordPress, I can say that the way I do OOP is largely based on what WordPress does. If WordPress improves, so will I, and many others will too. However, there is a difference between growing my knowledge of OOP alongside WordPress and a newbie trying to break into WordPress development after the fact. I think if it *seems* too complex, it may discourage some people from getting in (not necessarily a bad thing, mind you). It took both me and @welcher some time to wrap our minds around it, but I think in some ways the end product will actually be simpler than what is was before, once a dev cracks the entry barrier. And, because backward compatibility will be maintained, newbies can continue to use the old approach until they better understand the new underlying API. |