> On Apr 25, 2021, at 11:14 AM, Marc Nieper-Wißkirchen <xxxxxx@nieper-wisskirchen.de> wrote:
>
> I don't think that the package and library namespace should be mixed. Nor are library names like "(github.com/account/repo foo qux)" very nice, quite the contrary. And there should be no need to find a single library.

How do you define “nice”?  Note also that the go programming language uses essentially this approach.  The big advantage is clarity.  The name (github.com/account/repo foo qux) clearly indicates in the source code what is being imported.  Doing an (import (foo qux)), while shorter, is problematic because the meaning of (foo qux) will either be dependent on local installation details or it is dependent on a central registry of libraries (which involves a regulatory body). Using a URL in the library name naturally gives a unique name to the library and no one but the owner of github.com/account can use such a name (which solves the namespace management problem… i.e. no “higher authority” is needed).  I find these features “nice”!

Marc