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

[tony_marston404]

@TomB

Again, Robert C. Martin says Classes should be small and that a 70 method class is too large.

Any decision based on a simple count is ridiculous. Suppose I had a class for a database table which had 50 columns and I had a setter and getter for each. There’s 100 methods straight away, and the class doesn’t even do anything constructive yet.

@TomB

Coupling is when one class or method requires the existence of another to function.

When measuring software quality any “coupling” produced by inheritance can be totally ignored. It is only when module A calls module B that the degree of coupling can be affected by the developer.

@TomB

Because they are related concepts.

Both articles use the terms “responsibility” and “concern” in exactly the same context, so the terms are not merely related they are identical and interchangeable. I have yet to see any article which states that these two principles are different, explains why they are different, and gives examples of the different results produced by each.

@TomB

No, you purposefully mis-interpret them by quoting single sentences out of context because you want to use them to justify your existing code.

Just like you do.

@TomB

Riiight… there’s no such thing as “industry standard” or “academically recognised terms”. Where do you come up with this nonsense, do you even think about how stupid it sounds when you type it out?

I qualified that statement with that is universally accepted by all programmers. Just because one group produces a piece of paper with “best practices” as its title does not mean that everyone else immediately falls into line. Different groups have their own idea of what’s best for them.