Nothing here yet.
Nothing here yet.
No blogs yet.
The answers given by you and Mark are very insightful and fascinating. But there is one aspect in my mind that I want to shed light on to and that is Design Patterns. Correct me if I am wrong, aren't Design Patterns important and are heavily used in Frameworks. For example, Laravel makes use of MVC Pattern, Facades and IOC Container. So isn't it a sort of prerequisite to know design patterns before going to reveal the magic of frameworks. And secondly is it worth the effort to understand a framework. As a beginner, I have the perception that just like programming languages it will become easier to use and learn other frameworks, once I learn and understand a particular Backend-Framework. P.S. (Pardon me for the long comment & the possible holes in my knowledge)
Pardon me for my wrong judgement and unfair criticism. I've realized you answer is not opinion based, I just find it a bit incomplete. And yeah your argument about the constructors at the end seems very reasonable.
AARGH! as a Novice I find this very confusing. I guess I've to stop tiring myself over this and consider it as " This is how it works in PHP ". Your answer sounds logical, helpful indeed Thanks!
I understood the point, static methods and properties can be called directly by class name without any object instantiation, Correct! It is just that I am confused as to " Why PHP allows non-static methods to be called directly by class name without any object instantiation " & then on the other hand throws error when doing the same with properties. At present, my only best guess is this is how PHP works or in general Object Oriented Programming Languages work, correct me if I'm wrong.