All geek questions in one place

Is it always justified to write a large enough database-based PHP application procedurally and without MVC?

Sorry for the rather subjective question, but I was hoping to get an opinion from someone more experienced than me on this.

I'm pretty far from an ajax-based PHP application, and although I have a pretty good separation between markup and client-side behavior, my PHP is slowly getting a little messy. I do everything in order, breaking it into pieces and structuring in such a way that I don't have too many repetitions, but I am definitely starting to see how this can become a burden with enough code. So I read about OOP and MVC, and now I'm trying to decide if refactoring is worth it for CodeIgniter or Kohana. Intuitively, it seems that it will be more work than worth it, but I know that I can sing a little differently.

In your experience, it is believed that today it is absolutely serious to write a serious expression procedurally or there are certain types of applications that are better suited for procedural / structural programming.

+3
source share
2 answers

MVC and OOP are simply “ways,” among others. Yes, they are great, make it easy to write code, and are used a lot, but this is not the only way to develop the application.

For example, Drupal does not use any object-oriented code: it is all procedural ... And this is a great application that has great success, is used by many people, even on large sites, and for which many people have developed many modules ... even if it almost does not use any class / object!

I, personnaly, MVC / ; , , - , : , - , ^^

+7

, - , , . ( , "-" .)

, , , . (, , , .) , , , , , .

+1

Source: https://habr.com/ru/post/1724066/

More articles:


All Articles