Are today's major frameworks capable of enterprise capable applications?

[tony_marston404]

@TomB

tony_marston404:
Can you point to any authoritative article which says that inheritance produces tight coupling?

Wikipedia is not authoritative. Here’s an academic paper:

The ORIGINAL definition of coupling is defined thus

In software engineering, coupling is the manner and degree of interdependence between software modules; a measure of how closely connected two routines or modules are; the strength of the relationships between modules.

This is clearly limited to when one module calls another, not when one class inherits from another. The fact that some people have chosen to use the word “coupling” to describe the effects of inheritance is a silly mistake on their part. This is just as silly as the notion that inheritance breaks encapsulation.

If you bothered to read that article which you cited you would have read the following:

Classes (objects) are coupled three ways:

1. When a message is passed between objects, the objects are said to be coupled.
2. Classes are coupled when methods declared in one class use methods or attributes of the other classes.
3. Inheritance introduces significant tight coupling between superclasses and their subclasses.

Since good object-oriented design requires a balance between coupling and inheritance, coupling measures focus on non-inheritance coupling.

This quite clearly states that when examining code using various metrics that the effects of inheritance can be ignored.