Re: Module or Class Visibility, Season 2
On Wed, May 14, 2025 at 4:08 AM Rowan Tommins [IMSoP] <[email protected]>
wrote:
>
> What Michael Morris is talking about is really a completely different
> concept - it's more like "containers", in the sense of Docker, Kubernetes,
> etc, where different sections of code can be isolated, and declare classes
> with conflicting fully-qualified names. I don't think it's what most
> applications and libraries would want "modules" to be; it's probably best
> thought of as a completely separate feature.
>
>
Well, it's what Go calls "modules". It's confusing because I was being
truthful, not snarky, when I said "Ask 10 programmers for the definition of
module and expect 12 answers." I'm self trained, so I expect to get my
terms wrong from time to time. But I know enough to identify problems and
needs and I've tried to be clear on that.
I'm currently reading up on Phar and seeing exactly how suited it would be
as a foundation for a module system. I've also been reading on how go
approaches things, but go has package management baked into the compiler -
PHP outsources this to userland. I'm going to guess that's largely because
of lack of staff - PHP has no large backers (leeches like Facebook that use
it heavily and could back it yes, but not backers) and Go has Google.
Thread (13 messages)