How was the code organized before the use of the MVC architecture in web development?

Question

Software design

I started learning web development just a year ago and while getting into the back end, I was forced to understand how MVC works.
Due to the fact that I did not come across other methods of organizing code in web development, I had a question - were there other effective methods of organizing code?

Answer 1

Did not have. Look at the code of old open source projects. There is porridge.
Therefore, new versions of some old engines are being rewritten taking into account the knowledge gained.

Answer 2

No. In general, all this is logical and was even before the web, the principles of strong / weak connectivity and all that. In the context of PHP - before PHP was only the letter V in projects on the pluses. Since then a lot has changed.
Well, again, nothing can be more effective than loosely coupled systems, whether you call it MVC or something else, the essence of this does not change.

Answer 3

Previously, it was difficult to identify any patterns. There were projects where there was a complete mess, when both data processing and their display were in one file. But there were also projects that were somewhat similar to MVC, when templates were separated from the entire site structure into separate files.
Now along with MVC there are such design patterns as:
- MVP - ru.wikipedia.org/wiki/Model-View-Presenter
- MVVM - ru.wikipedia.org/wiki/Model-View-View_Model
- PAC - en.wikipedia. org/wiki/Presentation%E2%80%93abstrac...
- MOVE - habrahabr.ru/post/147038

Answer 4

Prior to PHP 5, there was no OOP, and almost all projection patterns involve the use of objects. They got out as best they could. It turned out differently. Basically what.