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

Anything calling itself a framework which does not exhibit the four characteristics mentioned in https://en.wikipedia.org/wiki/Software_framework has no right to call itself a framework.

Riiight so a peer reviewed journal is equal to a wikipedia article in authority. Really? I suggest you go and look up what academic references are and how peer review works.

But you do take concepts that come from academia and redefine them so they fit your existing code. There is a difference between theory and practice, of course, but that doesn’t mean that practice gets to redefine theoretical concepts. You don’t get to redefine relativity because you don’t like not being able to travel faster than the speed of light.

Because you clearly don’t understand what an authority is, who comes up with the concepts you abuse in the first place and even why they exist. You just see your own framework and then see someone say “SRP” and you then say “Well I must already be doing that” go look at the definition and try to make it fit, unsuccessfully, I might add.

Lets put it this way: If you were looking up a treatment for a disease would you trust wikipedia over a study in the BMJ? The same applies in computing, we just have different journals. IEEE is probably the most well known journal publisher in computing/engineering.

It also does not necessarily mean that a component should be implemented in multiple classes. You are reading what isn’t there.

Nowhere in either of Robert C. Martin’s articles (see http://blog.8thlight.com/uncle-bob/2014/05/01/Design-Damage.html and http://blog.8thlight.com/uncle-bob/2014/05/08/SingleReponsibilityPrinciple.html) does it mention that once you have separated your program logic into GUI logic, business logic and database logic that you should continue to split up each of those areas into smaller units. They DO NOT say that, so it is YOU who is reading what isn’t there.

Where does it say that?

Wikipedia says it clearly.

In object-oriented programming, the single responsibility principle states that every class should have responsibility over a single part of the functionality provided by the software, and that responsibility should be entirely encapsulated by the class. All its services should be narrowly aligned with that responsibility.


Robert C. Martin said this in the book Clean Code.

The person you like to cherry pick information from. You quote him when it suits you and you can take him out of context, but then ignore him when you are unable to do that. It’s amusing really.

Also, since you love wikipedia so much, please answer the question I asked earlier and you ignored (As you do with uncomfortable questions unless I ask you 10 times):

If SoC and SRP are the same thing, why are there two different wikipedia pages for them?

And this question please:

What are you trying to achieve/prove by coming here and showing that you have a decided to redefine common programming concepts when everyone else in the world already agrees what they mean?

The MVC design pattern specifically mentions three components or objects, so it is reasonable to assume that each of those objects can be supplied from its own class. To say otherwise is to read something which isn’t there.

I disagree. A Controller is responsible for (or concerned with) all control logic. A View is responsible for (or concerned with) all view logic. A Model is responsible for (or concerned with) all domain or business logic.

It is therefore reasonable to assume that I can have a single class for each.

“concerned with” and “responsible for” mean exactly the same thing.

In a purely english sense perhaps, however they have been used to describe particular concepts in OOP. It’s like saying “Car and Automobile mean exactly the same thing” ignoring the fact that “car” can also be used in the context of trains. In which case, they are not the same thing at all. Nuance really isn’t your strong point.

As does every programmer in the universe.

Question: What is the difference between Theory and Practice.
Answer: In Theory there is no difference but in Practice there is.

In practice a theory is sometimes toned down so that it can be applied in a practical way. Theory may define “purity” but sometimes in the real world a working solution can be quicker and cheaper to build than a 100% pure solution. It is a question of balance, of trade-offs.

So you are the only person who can decide which articles have “authority” and which are worthless? Pull the other one, it’s got bells on!!

I have learned not to trust every opinion by every so-called “expert”, especially government experts. How many “expert opinions” have been completely reversed by a different opinion a few years later?

That is EXACTLY what I have implemented. Each of my Model classes is responsible for the business rules associated with a single database table. I have separate classes which deal with control logic, view logic and data access logic. You may have a different opinion, but that doesn’t mean that your opinion is the only one worth having.

Confirmation bias much?

[citation needed] I think!

Unlike you, most people build their code to fit the underlying concepts.

But again, that doesn’t mean you get to redefine the theoretical terms to fit your application. So far you’ve redefined encapsulation, SRP, SoC, coupling and “software component” in order to fit your needs and make the claim “My code follows the concepts!!”. Instead, you should build your code based on the concepts, not redefine the concepts to fit your code.

I am not deciding anything at all. Peer Reviewed Journals are authoratitive because they are published after having extensive scrutinization by experts in the field. Nothing gets into a journal before being heavily critiqued by people at the top of the field. Again, I suggest you go and look up what peer review is because you clearly don’t understand it.

Exactly. And this is a good thing: New data comes along to show that the old theory was wrong and we change treatments based upon the new evidence. At any time the evidence can change, of course but your approach is ignoring the evidence and sticking to what you already have even if a new, measurably better treatment has come out and then claiming “The old treatment is better!!!” or saying “I’m already using the new treatment!!” by redefining what others mean.

That is why I have a separate Controller for each transaction pattern, not a single all-in-one Controller that deals with every pattern

That is why I have a separate View for each output format, not a single all-in-one View that deals with every format.

That is why I have a separate Model for each database table, not a single all-in-one Model that deals with every table.

So you see, I DO have many small classes and not a few big ones.

Again with redefining terms. Redefining “small” is a big step even for you. In what world is 120 methods and 50 variables “small”? Keep in mind Robert C. Martin himself inferred that 70 methods is a “god class”.

Wikipedia on MVC makes no mentions of objects.

No, it actually isn’t. Only you reason that it is reasonable.


Then what do you call your Default_Table class? It looks like a really big one to me.


[quote=“TomB, post:176, topic:191138”]
What are you trying to achieve/prove by coming here and showing that you have a decided to redefine common programming concepts …[/quote]
I am not redefining these concepts, just giving a different interpretation. If they were not so badly written in the first place there would be no room for mis-interpretation.

That is a ridiculous claim to make! No-one agrees on anything, which is why the internet is full of conflicting opinions.

You still didn’t answer the question: What are you trying to achieve by coming here and arguing that everyone else in the world is wrong?

And again, you ignored my other question:

If SoC and SRP are the same thing why are there separate wikipedia pages for them?

It is literally only you who is arguing about the meaning. There is plenty of discussion about how the concepts can be best applied but you reshape the concept to claim your application fits it. Don’t you see why that’s backwards?

So these words have different meanings in a different context??? And you can change the meaning to whatever you like??? You remind me of a certain fictional character:

Many words have different meanings in different contexts. Murder can mean different things if it’s in relation to people or crows. Boot can mean different things depending if you’re talking about a car or a piece of footwear. Foil has a different meaning if you’re talking about the material or what you’re going to do to someone’s plan, etc, etc…

It’s nice to see it’s not just programming languages you struggle with.

Ironically “It means what I choose it to mean” sums up your stance incredibly well.

So I have to ask: do you have any qualifications at all or just 30 years experience? I’d expect someone who’d done so much as an undergraduate degree (even 30 years ago) to understand the difference between a primary, secondary and tertiary source, why primary sources are more authoritative than tertiary sources (like wikipedia) and a have a basic understanding of peer review.

And if you don’t have any qualifications what makes you think you know more than researchers at the top of the field or people doing PhD level research such as myself?