3 ms·
I'm with @jeremyjh on this one. There was no management. There was a "fuck it. works for me." kind-of half-assed implementation that was frankly terrible when c
by masukomi 7y ago
I'm with @jeremyjh on this one. There was no management. There was a "fuck it. works for me." kind-of half-assed implementation that was frankly terrible when compared to ANY of its contemporaries. It spawned a ton of competing "package managers" that attempted to do a better job but none of them "won" (probably because none were officially sanctioned) so you ended up dealing with like six of them in order to manage the dependencies of whatever random project you tried to work with.
No-one "managed" the problem. They just sat and watch the community flail around for years.
- walterstucco 7y agoThat's exactly what happens when a tool is left open to community If the community cannot agree on a simple thing like the package manager, imagine what'll happen if it was in charge of evolving the language
- rightbyte 7y agoThat what's happen if the community has no say in what package manager is used or how it works and the community is not forced to use the official one and the community is not organized properly.
- Lazare 7y agoI would say it's what happens when a community is explicitly not allowed to solve a problem. PHP, for all its warts, is 1) very community driven and 2) solved their package management problems via the community (with Composer). Go was not allowed to do that, because everyone knew that any solution had to be blessed by Google.