3 ms·
Gists are quick and dirty. When I use a Gist, I don't need a full repo. A full repo could do the job, but it'd be like hauling groceries in the back of a dump t
by bradleyland 13y ago
Gists are quick and dirty. When I use a Gist, I don't need a full repo. A full repo could do the job, but it'd be like hauling groceries in the back of a dump truck.
Why do we "need" them? We don't, but they're nice to have. I have all sorts of things in my life that aren't needs, but I'm still glad I have them.
- Myrmornis 13y agoWhat is it about a full repo that makes you think it is heavyweight for the task?
- garblegarble 13y agoNot the original poster but from my perspective it's the lack of tools in github to manage the proliferation of repos. I'd like to categorise them when I'm browsing my own repos and expose those tags to other people: my hairbrained experiment repos, my serious OSS efforts, my fork-to-keep-a-stable-version-of-some-remote-project repos... I could do something like that by creating a load of organisations but it'd be nice if there was a simpler way. Gists provide a very primitive way to divide things up, but at least it's something!
- Myrmornis 13y agoYes, that's a good point. Although gists too is a flat list I think. But at least with gists and repos we have two flat lists.