Steven D'Aprano writes: > On Tue, May 25, 2021 at 04:24:39PM +0900, Stephen J. Turnbull wrote:
> It's not really purely cooperative. API consumers always want more than > the API designers are willing or able to give. True enough as stated, but "purely cooperative" doesn't mean "if I optimize, you get the best of all worlds". It means if we communicate, we can coordinate and get a good solution. If we don't communicate, generally we get a bad outcome. The situations you describe don't seem to have a lot of communication in the design of the APIs. There are situations where communication is difficult. Developer A provides an API tuned to Developer B's application, and later Developer C wants A's functionality but wants a different API. Or (as is frequently the case with open source) Developer A is both producer and the initial consumer of the API, and drops the producer on PyPI with an "as-is" notice, frustrating Developer C. Point is, you're right, and lack of communication between API producers and API consumers is why you're right. That is a problem for management; you can't engineer it away, neither with "private, protected, public", nor by avoiding them. Steve _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/5V2MBESTK2T5CNU4D5IT6ZONOFJBBU6F/ Code of Conduct: http://python.org/psf/codeofconduct/
