Would you agree this is the definition of a PHP framework?

[tony_marston404]

@s_molinari

tony_marston404:
So you are saying that the meaning of a word changes when it switches from singular to plural?? What a load of BS.

Are you saying, a person can simply ignore the meaning of a sentence, because a certain word is found within it and can be taken completely out of context? What a load of BS.

Show me where I have given a word in a sentence a meaning that is other than that which is found in the dictionary? To any reasonable and intelligent person the terms “responsible for” and “concerned with” mean the same thing. This in turn means that SRP and SoC mean exactly the same thing.

@s_molinari

SoC is about the software as a whole. It defines the need for separation of concerns, each concern being a set of responsibilities. You can say your monster class along with the other separated concerns follows SoC.

However, SRP is about the proper formatting of singular classes and defines that a class should have a single responsibility and reason for change.

I have already pointed you to several articles which use the terms “responsibility” and “concern” interchangeably, so it is obvious that they mean the same thing. Anyone who tries to say otherwise is merely being pedantic and is nit-picking over trivialities. Both of those principles talk about taking a monolithic piece of code and breaking it down into smaller units each of which has a single concern or responsibility. Robert C. Martin has said in more than one article that separating GUI logic from business logic from data access logic is “good” design, and that is precisely what I have done.

@s_molinari

With that definition, your 9000 class clearly breaks SRP.

I disagree. Saying that a class breaks SRP simply by counting the number of methods is completely unscientific. Each of my Model classes is responsible for the business rules associated with a single database table. It does not contain any control logic any view logic, or any database logic, so it fits Robert C. Martin’s description to a tee.

@s_molinari

http://weblogs.asp.net/arturtrosin/separation-of-concern-vs-single-responsibility-principle-soc-vs-srp

Here is an SE question, where everyone who answers is agreeing and they all agree they mean different things.

Just because some people share this opinion does not make it a valid opinion that should automatically be accepted by everyone.

@s_molinari

The SoC-Principle is strongly related to the Single Responsibility Principle (SRP) with concerns being a superset of responsibilities. In an ideal case, each responsibility consists of exactly one concern namely it’s core functionality. Often though multiple concerns are mixed inside one responsibility since it’s technically sometimes unavoidable. Therefore keep in mind that the SoC does not say ‘one responsibility should have only one concern’, but it says ‘concerns should be separated’.

In the two articles https://en.wikipedia.org/wiki/Single_responsibility_principle and https://en.wikipedia.org/wiki/Separation_of_concerns there is no place where it says “this principle is different from the other”. They both talk about breaking monolithic software into a collection of modules or classes.

If SoC is different from SRP, then why does it not have its own place in SOLID (https://en.wikipedia.org/wiki/SOLID_(object-oriented_design))?

@s_molinari

Now, for your second challenge. (the first one of finding an MVC framework with only three classes was a fail).

How about this one https://r.je/mvc-tutorial-real-application-example.html

The fact that MVC could be implemented with more than one class does not mean that it should. Most developers use only three, and there is nothing wrong with that. Personally I use four as I prefer to have all database access in its own class, which means splitting the Model into two separate parts.

@s_molinari

Find an article on the Internet, where it is clearly stated that SoC and SRP are exactly the one and the same concepts.

How about this one - http://tenera-it.be/blog/2012/02/code-readability-vs-socsrp/
Or this one by Robert C. Martin - http://blog.8thlight.com/uncle-bob/2014/05/08/SingleReponsibilityPrinciple.html
Or this one - http://aspiringcraftsman.com/2008/01/03/art-of-separation-of-concerns/