This doesn’t address moves at all? I might need to read it again but I don’t think it’s as easy as the author claims it is.
And not pointing out that a `foo(const std::shared_ptr<Widget>& widget);` should most likely become a plain `foo(const Widget& widget);` with a `*widget_ptr` dereference at the callsite.
You can solve problems with them but the moment I see them in code it raises flags that make me think someone gave up solving the actual problem at hand and “this seemed to work”.
I’ve seen many an otherwise good looking code base paint itself into corners over object ownership, life cycles and resource reclamation.