This is great because it helps with understanding why for some long-standing projects it may not be feasible to incrementally change toward new API. And, it can be worth considering pioneering new breaking change versions that would bring new capabilities into being.
It's a thorough explanation for those who understand PostgreSQL internals. It probably needs some time to understand the ideas. They are elegant in my opinion. Thanks to the author!
