Re: Module or Class Visibility, Season 2

On Tue, May 20, 2025 at 6:18 PM Rowan Tommins [IMSoP] <imsop.php@rwec.co.uk> wrote: > > > On 20 May 2025 15:04:49 BST, Michael Morris <tendoaki@gmail.com> wrote: > >The Problem: Interoperability. > > > >That's really it. Scenario > >Alice provides whatchamacallit A that depends on other whatchamacallit D > to > >work. > >Bob provides whatchamacallit B that also depends on D. > >Charles is using A and B. > >D gets updated with a new incompatible API to its prior version. > >Alice publishes an update which includes a security fix. > >Bob retired. > >Charles, who can't program, can't update to Alice's latest code. His site > >eventually gets pwned. > > Let me correct something here. The whole reason I was bringing in the > distinction between "module" and "container" is that B and C are one kind > of thing, but D is a *different* kind of thing. > > D is something like Guzzle. There is zero motivation for Guzzle to be > rewritten in a way that forces its dependencies to be isolated. It depends > on packages like "psr/http-client" whose *entire purpose* is to define > interfaces that multiple packages agree on. > > A, meanwhile, isn't a thing at all; it's just any old PHP code I'll stop you there. You are deliberately misrepresenting what I wrote and even a cursory glance at it makes that clear. You are not trying to be constructive in any way, you're trolling.