What is the point of gists?

http://pastebin.com/EVZUUmaW

by Myrmornis • 12 years ago

3 13 12 years ago

pastebin.com

nanofortnight• 12 years ago

My use of gists is pretty much the same as your present use of pastebin.

* Writing long texts to link back to. Bonus is they're editable.

* Giving short snippets of code or log files.

* Linking to a short amount of text and a couple of pictures. Unlike pastebin you can include diagrams and such in your text.

I have also used gists to host full (but short) programs or libraries, but that is usually as a response to a question on IRC or over Twitter.

bradleyland2• 12 years ago

Gists are forkable too. Gists are very useful for getting input on small snippets of code the might not otherwise be accessible to everyone being asked to provide feedback.

Myrmornis5• 12 years ago

Why not use a regular git repo? Why do we need two species of git repo?

Myrmornis5• 12 years ago

Linking to a short amount of text and a couple of pictures. Unlike pastebin you can include diagrams and such in your text.

OK, that makes sense. Could also be implemented as a git repo containing only README.md, but gist gives you more flexibility as everything doesn't have to be embedded in markdown.

nodata• 12 years ago

Ironically could have been posted as a gist.

heinrich5991• 12 years ago

My IP is blocked at pastebin, can someone paste the text here, please?

vitorbaptistaa• 12 years ago

The text is:

"I use git and github a lot and have very few complaints, and yet I have failed to see the use of gists.

- What is wrong with standard repo + README? - No way of converting a standard repo into a "gist" repo.

When I work on a code project, even some random one-off script, I track its evolution in a git repo. So if it doesn't naturally belong in an existing repo, I create a new repo. As soon as I have something that I don't want to lose, I'll make an initial commit. The commands involved are near instantaneous and they bring huge benefits.

Now, I want to share this script. Can I turn my repo into a gist? No, I don't believe so.

So what is the workflow?

1. Start work 2. Get to a point you want to share with others, without ever having committed 3. Use web UI to create gist 4. Paste work into gist and save 5. Edit, paste, iterate

1. Decide to start project 2. Use web UI to create gist 3. Clone gist repo 4. Rename it so it's not just a large integer 5. Start work 6. Commit and push gist to remote

I don't hear much criticism of gists so hopefully I am missing something. But at the moment it seems to me that if you want history, use a normal git repo. And if you don't want history, use a paste buffer with no versioning features"

numberwhun• 12 years ago

I tend to use gists as a sort of snippets library (of sorts). I always have bits of useful code that I am going to need again at some time and having something like a gist is quite handy.

Myrmornis5• 12 years ago

Yes, personally I use a single "miscellaneous" repo for this purpose. Do you not find that, when working on one of those snippets, you want to commit your changes (in your present command line environment)? Copying and pasting into a web browser doesn't seem an attractive way to commit. I'd be interested to hear what your workflow is.

What is the point of gists?

Related Stories