> I don’t know what that is

its a standard output from `go doc`, rendered as HTML. if you dont recognize that, then you aren't really in a position to be commenting on the topic. nothing is stopping anyone from pinning to a tag:

https://github.com/git-lfs/git-lfs/tags

or even a commit and relying on a specific version of the software. yes upgrades might be painful but a module IS available.

That you technically have the ability to call into an internal module does not in any way constitute it "offering itself up as a library", and doesn't make it effectively useful in that way.

It is a module. It is available. It does not offer itself up as a library.

> It is a module.

> It does not offer itself up as a library.

in Go code, those are the same thing.

A library and a module are the same. Having an open and available module does not make it "offered up as a library," was the point I was trying (and failing, evidently), to make.

You made the point perfectly. So did the docs in the first place. It's not on you that someone decides not to agree the sky is blue because they use their own definition of blue.

Please don't cross into personal attack. It destroys what this site is for, and you can easily make your substantive points without it.

If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.

Anything's a library if you're sufficiently motivated

- Hyrum Wright, probably

I made Kubernetes into a library once. Like the apiserver and default controllers, running in-process. Copying and pasting were involved. I was not expecting support.

If code is out there under a compatible license, you can do whatever you want with it. If it breaks, you get to keep both pieces.