Developers often argue about frameworks. Many believe that WordPress is not a framework. But is that really the case?
A framework (sometimes framework; an Anglicism, a neologism of framework – skeleton, carcass, framework, structure) is a software platform that defines the structure of a software system; software that facilitates the development and integration of various components of a large software project.
In general, this should be sufficient for 50% of people. From the definition we understand that WP is indeed a framework.
But why do 99% of PHP coders think this isn’t the case?
WordPress is not a framework, but a CMS
In general, this statement is also true. Yes, we can use WordPress as a constructor.
We don’t even have to write code. We can use NoCode, ZeroCode and LowCode strategies. These are so-called configuration-based approaches, where you can manage the entire project online without changing the code.
Discover the most exciting things in the world of excitement – Las Atlantis live casino
Is this good or bad?
It is good for business: costs are reduced by a factor of 10. In 99% of cases.
It’s bad for programmers: firstly, they are out of work, and secondly, such a system is much more difficult to manage; you have to be able to think, and not many people can do that.
And from this it becomes clear why programmers hate WordPress: it is a normal primitive survival reflex. You must be against those who take your bread and butter. WP deprives programmers of their bread and butter, which is why it should be vilified.
You might think so, but there are nuances…
However, there is also some truth in it
Frameworks are inherently tailored to code and are driven by the desires of programmers: to make the code beautiful, to be able to write autotests with a few clicks, to be able to build migrations easily, to make queues work clearly in the background, and so on.
In WP all this can be done too, it is practiced in some form, but there are no clear, understandable solutions. And every major project comes up with its own solutions here.
However, this is not a reason to say that WordPress is not a framework. It is more accurate to say that it is a framework tailored to the needs of a no-code CMS, and it does not have ready-made tools for limited tasks. You’ll have to come up with them yourself. This is a problem for many. Therefore, there are many cases where it is really better to use something like Laravel or Symfony, because those frameworks have some tools for narrow-necked tasks.
Conclusion
In general, it is not a question about WordPress whether it is a framework or not. The question is who uses it and how.
You can use it as a constructor and not worry about it. You don’t need to know architecture, code patterns and other fancy words; just click and work.
You can use it as a framework, but you need to know what the three types of OOP are, what AOP is, what EDA is, and how SOLID differs from GRASP.
#WordPress #framework #CMS #reset