3 ms·
In an ideal world every project had its own registry. Those centralized registries/package managers that are baked into tools are one of the reasons why hijacki
by foepys 4y ago
In an ideal world every project had its own registry. Those centralized registries/package managers that are baked into tools are one of the reasons why hijacking namespaces (and typos of them) is even possible and so bad.
Externalizing hosting costs to other parties is very attractive but if you are truly open source you can tell everybody to build the packages themselves from source and provide a script (or in this case a large Dockerfile) for that. No hosting of binary images necessary for small projects.
Especially since a lot of open source projects are not used by other OSS but by large organizations I don't see the need to burden others with the costs for these businesses. Spinning this into "Docker hates Open Source" is absolutely missing the point.
Linux distributions figured out decades ago that universities are willing to help out with decentralized distribution of their binaries. Why shouldn't this work for other essential OSS as well?
- adql 4y agoThat's one reason I like Go's model of "import is just an URL path" Sure it has some problems but it's far preferable than to be slaved to single entity controlling repo
- bioemerl 4y agoWe need some sort of system that's both distributed (anyone can host) and centralized (one url for a download that doesn't require someone to keep a server up with an ssl certificate needing monthly renewal until the end of time). We also need to set it up so that the default is that your server using the project also helps host the stuff it needs to run.