My favorite new feature: you can finally search through your own gists!
I use gists all day every day: it's where I dump and share pieces of reusable code. It's always been a huge pain to search for something you know you gisted, but can no longer find without browsing through 20 pages of 3-line excerpts. Search makes this a million times better.
I find that github has always had poor to okay search capabilities.
For example, have you ever tried to search for a repo name, only to find 1000 forks? wat. Ever tried to search issues for a specific issue, only to find no results, removing a word or two to get a less accurate search.
Search for me is about discoverability. And github is for developers for the most part.
As a developer I want discoverability for code! I want regex features (like in google code search), better matches. Ways to compress my search results down. Search tags code:'if Awesome()'.
I just feel they could be doing so much better in this area.
Gist is our first entry into Better Search. With the amount of code we index (and the unique problems of searching source code as opposed to prose), it's not something we can change overnight.
The lack of search is the main reason I created http://gistedapp.herokuapp.com. Unfortunately I still find their search lacking in a few fundamental ways:
* it is (surprisingly?) case sensitive
* it only searches titles, not file contents
* the UI feels disconnected from the main gist area, making it unclear whether its a search of all Gists (like the previous version) or a personal search.
Fortunately, this update indicates they're paying attention to a much-used part of their product that was starting to feel neglected. At their pace of improvement I can't see these holes remaining for too long.
Now, hope they add back the ability to be notified when there's a comment on your gist (which Gisted supports)!
GitHub seems to be in the midst of a spree of new non-trivial features: in the past week or so, there have been 7 blog posts, every one introducing something new!
gist.github was way behind the rest of Github for a long time. It's good to see they've finally released this because they've no doubt been working on it for a while.
I think "Secret Gist" is just a renaming of "Private Gist" which has existed for a while: only people with the url will see it. It's a better and more accurate name, for sure.
I do wish there was a true "private" gist, though, for easily preventing people I don't specify from seeing it. I'd love to be able to use it to trade code examples for work, but there's nothing to prevent someone from accidentally pasting the url into the wrong irc window and showing the world our internals.
I know HN doesn't believe in a comment where an upvote will suffice, but the first thing I searched this thread was for "pull request" and by golly, I think they would be a great addition also.
In my opinion: In a couple of years we will not use Emacs or Visual Studio or anything like that: Most of programming will be done socially in Github via small changes directly from the website, from hundreds of people... it'd simplify the process of collaborative programming a lot.
> Most of programming will be done socially [...] via
> small changes [...] from hundreds of people
This seems a little extreme. I'd venture that right now 'most of programming' is private code, or small side projects/toy code (i.e. single-developer projects).
I'd think that the total SLOC in side/single-developer projects is miniscule compared to the total SLOC in social projects (e.g. Linux, GCC, Emacs, etc.), and even smaller compared to the SLOC in private/corporate code-bases.
Most of programming will be done socially in Github via small changes directly from the website, from hundreds of people
What a nightmare.
I prefer very small teams whose members each have particular responsibilities so they're not stepping on each other, testing code before pushing out to the public.
As someone who's been on emacs the better part of a decade now, I find your opinion adorable and invite you to wrestle my editor/ide/im client/mail client/friend/lover from my cold, dead, RSI'd fingers.
As someone who's always worked alone, I also find your opinion adorable, and will code socially when someone manages to hack their way into my ultra secure coding vault. Which I admittedly let people into for pairing. Sometimes.
Collaborative doesn't necessarily mean synchronous. We learned this building the real time building system in second life. Sometimes you just want to sit in your corner and know no one else is gonna come in, and not having that ability cuts off a huge portion of people who just don't work well in that circumstance. It's awesome to work offline, alone.
I hope we get to see Collections for gists, because I am finding them really unmanageable otherwise, and there is little incentive for people to browse through them otherwise.
A collection would just be a category of gists in a category like "Idiomatic Python examples", "Django snippets", and so on.
I think people use gists in a fundamentally different way (I do), and I guess you could argue that gists are mainly for viewing and sharing whereas repos are for cloning/downloads.
Think Collections as Pinterest boards for code, perhaps. :)
Gists could be social, whereas repos are more self-serving and utilitarian in the sense of scratching an itch. Or at least they could be.
Same here. I have lots of snippets (in JS, Python, Go,etc..). Managing them is a pain. Also I have some that I use for my blog examples however executing them alone doesnt do anything. It would be great if I could organize them.
Oh yeah, right. I forget the concept of using gists in blog posts, but I guess it's because I quit that thought because of how much of a mess it leaves behind in your gist list.
Agreed- I've used gists heavily in my blog posts and they look pretty terrible right now. I sent feedback to Github via Twitter. Hopefully they'll fix it quickly.
Fortunately, I implemented a cache layer on top of GitHub's API recently, so many examples are working on http://bl.ocks.org. But only those that are lucky enough not to get a connection timeout. Hopefully the API will be back up soon!
I'm also a bit sad that they're still using document.write for the embeds. That breaks on any site that uses Ajax-like page loading and is bad practice in general.
As many have already said, Github just keeps delivering quality, well-conceived and well-integrated updates. I hope they keep coming.
Now for my shameless plug:
If you use Gist as a means to share web-related snippets, you might be amazed by the Plunker editor (http://plnkr.co/edit/). It was inspired by Gist, but will let you actually 'run' your code (and will do some other cool stuff like real-time collaboration, previewing and linting). This tool has become quite popular in the AngularJS community and I hope to see more groups get on board in the future!
It's about time. I've been waiting for Github to overhaul the Gists functionality, I've been ever-increasingly relying on it to store my snippets as well as posting code in blog posts, and being able to search through your own Gists is a MASSIVE addition.
I've really been loving all of these Github updates the past year, they've been killing it and it's good to see they've finally given Gist some love.
Heads up, opening a Gist to edit/view from my list in a new tab (CTRL + clicking) doesn't work in Chrome 21.0.1180.75. The Stylesheet doesn't seem to load, not sure if this is an individual issue on my system.
I'd love to see the ability to print (with the wonderful formating in-tact, and none of the interface) directly from my Gists. There are various bookmarklets out in the wild that attempt to do this, all of which are of course broken after this update.
I just had a need to do this with a bit of documentation I was writing. Ended up modifying the DOM to show/hide what I wanted and allow the screen stylesheet to be used in printing (to PDF).
93 comments
[ 2.8 ms ] story [ 144 ms ] threadI use gists all day every day: it's where I dump and share pieces of reusable code. It's always been a huge pain to search for something you know you gisted, but can no longer find without browsing through 20 pages of 3-line excerpts. Search makes this a million times better.
The new code editor is also pretty sweet!
--- Somewhat OT:
I find that github has always had poor to okay search capabilities.
For example, have you ever tried to search for a repo name, only to find 1000 forks? wat. Ever tried to search issues for a specific issue, only to find no results, removing a word or two to get a less accurate search.
Search for me is about discoverability. And github is for developers for the most part.
As a developer I want discoverability for code! I want regex features (like in google code search), better matches. Ways to compress my search results down. Search tags code:'if Awesome()'.
I just feel they could be doing so much better in this area.
* it is (surprisingly?) case sensitive * it only searches titles, not file contents * the UI feels disconnected from the main gist area, making it unclear whether its a search of all Gists (like the previous version) or a personal search.
Fortunately, this update indicates they're paying attention to a much-used part of their product that was starting to feel neglected. At their pace of improvement I can't see these holes remaining for too long.
Now, hope they add back the ability to be notified when there's a comment on your gist (which Gisted supports)!
(Christmas spirit, maybe?)
gist.github was way behind the rest of Github for a long time. It's good to see they've finally released this because they've no doubt been working on it for a while.
I do wish there was a true "private" gist, though, for easily preventing people I don't specify from seeing it. I'd love to be able to use it to trade code examples for work, but there's nothing to prevent someone from accidentally pasting the url into the wrong irc window and showing the world our internals.
Still wishing I could get Gist pull requests or merge forks of my Gist from the UI.
In my opinion: In a couple of years we will not use Emacs or Visual Studio or anything like that: Most of programming will be done socially in Github via small changes directly from the website, from hundreds of people... it'd simplify the process of collaborative programming a lot.
Of course, I'd never leave Emacs for Github when creating software from scratch or doing anything big.
A couple of decades, maybe.
Even then I disagree, but it's at least plausible.
Years though? I think you're over estimating how quickly this could possible happen.
What a nightmare.
I prefer very small teams whose members each have particular responsibilities so they're not stepping on each other, testing code before pushing out to the public.
As someone who's always worked alone, I also find your opinion adorable, and will code socially when someone manages to hack their way into my ultra secure coding vault. Which I admittedly let people into for pairing. Sometimes.
Collaborative doesn't necessarily mean synchronous. We learned this building the real time building system in second life. Sometimes you just want to sit in your corner and know no one else is gonna come in, and not having that ability cuts off a huge portion of people who just don't work well in that circumstance. It's awesome to work offline, alone.
https://github.com/mattn/gist-vim
Related discussion: http://stackoverflow.com/questions/11456558/markdown-not-ren...
A collection would just be a category of gists in a category like "Idiomatic Python examples", "Django snippets", and so on.
I think people use gists in a fundamentally different way (I do), and I guess you could argue that gists are mainly for viewing and sharing whereas repos are for cloning/downloads.
Think Collections as Pinterest boards for code, perhaps. :)
Gists could be social, whereas repos are more self-serving and utilitarian in the sense of scratching an itch. Or at least they could be.
http://gist.io/3135754
http://bl.ocks.org/1353700
Two of my favorite gist frontends, broken :(
I'm also having an issue with Plunker as legacy templates are pulled from Gist and are currently broken.
Fortunately, I implemented a cache layer on top of GitHub's API recently, so many examples are working on http://bl.ocks.org. But only those that are lucky enough not to get a connection timeout. Hopefully the API will be back up soon!
Now for my shameless plug:
If you use Gist as a means to share web-related snippets, you might be amazed by the Plunker editor (http://plnkr.co/edit/). It was inspired by Gist, but will let you actually 'run' your code (and will do some other cool stuff like real-time collaboration, previewing and linting). This tool has become quite popular in the AngularJS community and I hope to see more groups get on board in the future!
http://plnkr.co/edit/gist:1136236?p=preview is a snippet by the unbelievable Mike Bostock pulled directly from Gist.
I've really been loving all of these Github updates the past year, they've been killing it and it's good to see they've finally given Gist some love.
I don't see a way to post gists directly from an editor like Sublime, but I'll be all over that when I find it.
https://github.com/bgreenlee/sublime-github
[1] https://gist.github.com/auth/failure?message=timeout&ori...
I just had a need to do this with a bit of documentation I was writing. Ended up modifying the DOM to show/hide what I wanted and allow the screen stylesheet to be used in printing (to PDF).