News for hackers. Stuff that matters.
Re:Snipt: Long-term memory for coders by rawsyntax on Thursday June 02, 2011 @05:22PM (#2614042)
Personally I prefer to use github gists
Re:Snipt: Long-term memory for coders by nicksergeant on Thursday June 02, 2011 @06:35PM (#2614292)
Yeah, that's my main competitor. Their API is lacking, though: http://develop.github.com/p/gist.html

So, I'm trying to fill that void.

Re:Snipt: Long-term memory for coders by abraham on Thursday June 02, 2011 @09:57PM (#2614857)
GitHub beefed up the Gist API in v3: http://developer.github.com/v3/gists/
Re:Snipt: Long-term memory for coders by nicksergeant on Thursday June 02, 2011 @11:13PM (#2615016)
Ah, nice! Hadn't seen that.
Re:Snipt: Long-term memory for coders by d0m on Thursday June 02, 2011 @04:35PM (#2613845)
On the main page:

  GRANT ALL PRIVILEGES ON my_database.* 
  TO 'my_user'@'localhost'
  IDENTIFIED BY 'my_password' 
  WITH GRANT OPTION;
Couldn't have shown a better example!
Re:Snipt: Long-term memory for coders by follower on Saturday June 04, 2011 @03:35PM (#2620268)
I like the "long-term memory for coders" tag line--it gets the idea across well.

I've been working on a project--Labradoc--that approaches a similar idea from a different direction: http://www.labradoc.com/

My goal is to encourage developers to take notes as they go to both help them and help other people looking for the information later. From my own experience I've found a "lab notebook" style of site has been valuable both for me and other people. And it tends to be pretty low overhead.

A longer term feature I was considering was making individual entries browsable as "tips" for particular technologies but that's still on the TODO list for me.

I think there's some interesting areas to explore in the spaces between services like GitHub gists, Stack Overflow and Instructables.

Re:Snipt: Long-term memory for coders by chrismetcalf on Thursday June 02, 2011 @04:27PM (#2613806)
This plus a vim plugin for browsing snips would be awesome.
Re:Snipt: Long-term memory for coders by nicksergeant on Thursday June 02, 2011 @04:28PM (#2613812)
As soon as the API is built out (it's already kinda-sorta built: http://snipt.net/api), this should be trivial.
Re:Snipt: Long-term memory for coders by MrNibbles on Thursday June 02, 2011 @07:37PM (#2614505)
Looks like a neat service, but browsing the public javascript 'snips' there is a large amount of quite terrible code that i wouldn't recommend anyone uses.

Not that this is in any way detriment to the service itself which looks good, merely a warning.

Re:Snipt: Long-term memory for coders by nicksergeant on Thursday June 02, 2011 @11:17PM (#2615026)
Yeah, definitely. The site started out as a place where I could organize my (private) command snippets, and kinda went from there. People wanted to make some public.
Re:Snipt: Long-term memory for coders by Raphael on Thursday June 02, 2011 @09:51PM (#2614840)
Signed in with OpenID, and Snipt prompts me to make a new account. I don't wanna.
Re:Snipt: Long-term memory for coders by cmelbye on Friday June 03, 2011 @09:33AM (#2616253)
I truly do not understand the point of OpenID if the website is just going to ask you to provide sign up information that it could've just asked for from your OpenID provider.
Re:Snipt: Long-term memory for coders by nicksergeant on Thursday June 02, 2011 @11:14PM (#2615020)
OpenID is going up in a smoke for the new version. Back to traditional accounts.
Re:Snipt: Long-term memory for coders by avidal on Friday June 03, 2011 @09:50AM (#2616314)
Mind explaining why? I don't really need yet another account.
Re:Snipt: Long-term memory for coders by nicksergeant on Friday June 03, 2011 @09:55AM (#2616336)
OpenID is a PITA to support on the backend. It's another layer that doesn't need to exist. A bunch of providers are doing away with OpenID, like Slicehost, 37signals, etc.

From a UX perspective, I'm not convinced OpenID is any more convenient than a traditional u/p. I use 1Password to manage my logins, it works perfectly. For many other reasons, everyone should be using 1P or some password management program, as well.

Re:Snipt: Long-term memory for coders by nicksergeant on Friday June 03, 2011 @10:08AM (#2616374)
Actually, Slicehost might not be getting rid of it. Not sure where I got that info.
Re:Snipt: Long-term memory for coders by iAinsley on Thursday June 02, 2011 @07:21PM (#2614446)
Snippets rocks, but a big time GUI wouldn't be so bad. A killer feature like textexpander would blow the top off snipt.
Re:Snipt: Long-term memory for coders by whackedspinach on Thursday June 02, 2011 @07:28PM (#2614475)
I just took a look at it and was considering buying it. Does it have any sort of cross-computer or cloud synchronization? Or is that how Snipt is different?
Re:Snipt: Long-term memory for coders by abraham on Thursday June 02, 2011 @09:56PM (#2614852)
It would be awesome if you could sort by the number of favorites.
Re:Snipt: Long-term memory for coders by res0nat0r on Thursday June 02, 2011 @08:09PM (#2614599)
Looks like github gists without the versioning.
Re:Snipt: Long-term memory for coders by x0t on Thursday June 02, 2011 @09:51PM (#2614839)
I don't think you can tag gists. Snipt's searching/tagging looks a little better.
Re:Snipt: Long-term memory for coders by jackolas on Thursday June 02, 2011 @10:39PM (#2614941)
Are the tags parsed our from the tools used or user provided?
Re:Snipt: Long-term memory for coders by nicksergeant on Thursday June 02, 2011 @11:15PM (#2615022)
User provided.
Re:Snipt: Long-term memory for coders by neuroelectronic on Thursday June 02, 2011 @07:06PM (#2614388)
Just in case you didn't want to use one of the other 1,000,000 options.
Re:Snipt: Long-term memory for coders by Koldark on Thursday June 02, 2011 @04:23PM (#2613783)
Isn't that what Evernote is for?
Re:Snipt: Long-term memory for coders by dasil003 on Thursday June 02, 2011 @04:26PM (#2613802)
Personally I'm a big fan of Snippets for OS X (http://www.snippetsapp.com/) The killer feature is Command-Option-V to autocomplete the snippet you want to paste.

I gave up on Evernote because of the totally broken text formatting.

Re:Snipt: Long-term memory for coders by nicksergeant on Thursday June 02, 2011 @04:30PM (#2613817)
Snippets is a nice app. I tried it a while back. If we can get them to interface with the Snipt API when it's finished, it'd be a great desktop UI for Snipt.
Re:Snipt: Long-term memory for coders by prudnikov on Friday June 03, 2011 @07:42AM (#2615950)
Do you need an integration with the Snipt to have your snippets available online? Any other reasons?
Re:Snipt: Long-term memory for coders by shennyg on Friday June 03, 2011 @01:01AM (#2615213)
Evernote works but it just isn't the right tool for the right job.

I use Evernote for remembering pretty much everything else but the text formatting really killed it for me, I want raw unformatted text.

I currently use and recommend snippets app but the dropbox syncing between multiple computers isn't the best when there are conflicts.

Snippets app was forked into another project. I cannot remember the name offhand but it looks like it may be going into a better direction.

Re:Snipt: Long-term memory for coders by nicksergeant on Thursday June 02, 2011 @04:26PM (#2613799)
Evernote doesn't do syntax highlighting, from what I remember. Also, can I make a note public if I want?

(it's been ages since I last tried Evernote)

Re:Snipt: Long-term memory for coders by 5l on Thursday June 02, 2011 @08:08PM (#2614590)
You can make notes public, and although you can't do syntax highlighting directly, you can copy already highlighted text into a note.