Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
Its time to stop! Please stop advising OOP with or without reason. This is a great approach to simplify readability, increase reusability, and simplify extensibility. But it is not needed everywhere!
If you are creating a site consisting of 2 text blocks and a feedback form, in 95% of cases you do not need OOP. Stop lugging packages with hundreds of dependencies to perform a basic operation once... OOP has its own well-defined use case, described in hundreds of articles all over the Internet, including in relation to php.
Therefore, answering the question of the TS - yes, it is relevant, but it is worth correctly assessing the need and applicability, depending on the task. To do this, you need to have some experience and study other paradigms.
Naturally, if you are able to maintain and expand it without making the project [email protected]
But you don't have to do that. Believe me, with objects it will be much easier for you
In sense "whether procedural is actual"?
A) A procedural context is normal within any class.
B) There are a lot of things (extensions, helpers, mappings) in various paradigms (MVC, MVP, etc.) that it makes no sense to roll into an OOP context. Literally pointless.
There are tasks of various levels of complexity (complexity -> "complexity" -> multicomponent), applications and architectures, for their solution there are different methods - OOP, procedural context and its varieties. And all this within one project.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question