Firstly, great article. Well explained and well illustrated.

Secondly, anecdotally I would say working with different teams for the last 15 years, composition invariably leads to silos and uneven adoption within teams. There are folks who grok it and apply it right away, there are folks who prefer explicit statement order and declaration. As the system grows in complexity and personnel, you grow a team from 6 to 12 and then to 18 unless a large majority therein can actually understand the concept and apply it correctly, you’ll end up with a code base that only a few can actually do meaningful work on.