3 ms·
Don't blame GitHub for Go's clearly broken dependency solutions. What everybody should have learned after so many incidents like this is this: an artifact shoul
by edem 9y ago
Don't blame GitHub for Go's clearly broken dependency solutions. What everybody should have learned after so many incidents like this is this: an artifact should only be deletable by nuclear fire
GitHub has a name squatting policy for a reason. I have multiple "names" because some guy's repo who abandoned GitHub years ago was released and I was able to reuse it for my own brand.
This is like saying if I buy a domain it should be mine for eternity even if it is no longer useful for me.
More about the squatting policy here: https://help.github.com/articles/name-squatting-policy/ https://help.github.com/articles/name-squatting-policy/