If you can explain your site in words that don't require very specific domain knowledge, I think that might broaden appeal.
I think this way of pitching is dangerous for two reasons:
1. Many potential users of the product (Kurikku) will not know about the thing it's being defined in relation to (Rap Genius), and will not understand that they should check it out
2. Those that do know might make a different comparison than you. I might say "It's like Github for music!" and you will think "Oh, so you put in scores and people can collaborate -- just like with code on Github!", but I was thinking "You store your personal music library in the cloud and you can clone it to all your machines -- just like with code on Github!" While you intend the comparison to be a way to explain a lot with just a few words, in reality it might be interpreted all wrong, giving users entirely unsuitable expectations when checking it out.
So, please try to communicate clearly about the thing you have made using every day words. Good luck :)
Am avid user of Rap Genius. Can confirm it is an amazing pitch.
Here's an example, from Nas' It ain't hard to tell:
"I drink Moet with Medusa, give her shotguns in hell"
I know Moet and Medusa, but I didn't know what "giving shotguns" meant. So I go to Rapgenius, click that line and it says: "To “shotgun” is to inhale from a pipe or other smoking device, followed shortly by an exhalation into someone else’s mouth."
Ah! So he exhaled weed smoke into Medusa's mouth, effectively stoning her. That was smart. Cool.
So imagine I'm reading official documentation, say "10 minutes to Pandas". I come across this line:
df = pd.DataFrame(np.random.randn(10, 4))
Nothing revolutionary, but it is a valuable idea and worth a shot. Of course, RapGenius could just launch CodeGenius and get that market instantly.
Kurikku = crowd sourcing explanations of computer code. Also brilliant useful, probably won't have as much traction as Rap Genius just b/c there are many more people in the world interested in lyrics than in computer code, but it will probably find a StackOverflow-level popularity, which would be quite a success.
That at least gives me an idea of what's going on.
And the beauty here is having people other than the original programmer add comments. There are a lot of open source projects on which I'd love to see this.
There are lots of ways to extend this concept too. I echo what joeconway wrote - having a way to filter and view the comments in a tutorial-like fashion would be great. Having a way to somehow submit patches and fixes back to the original source could be cool too. And offering this as a tool for computer science professors, programming instructors, and other educators (e.g. giving the comments in their example code a nice UI, almost like a documentation generator) could be interesting.
FYI, I just noticed the other tool, Noted Code, in the comments here. I prefer how Noted Code puts the comments and code side-by-side. Perhaps there could be a toggle for both views.
Just some random thoughts. Keep up the good work!
Or as a short URL: https://notedcode.com/n/02d0c232
This is a lot more difficult than you might think. I spent a fair amount of time implementing the solution to keeping the annotations in the right place when the code changes.
What do you guys think?
Hover line 5, and move the mouse straight down to line 6. The tooltip will remain the same.
The tool has it's applications in education. Good work. Just please redesign the homepage, because it looks like a mobile web site right now ;)
Also I really liked that documentation thing someone showed us a while ago... It put code on one side and annotation paragraphs on the other, and despite being very simple I think it did a very good job of making the code and annotations easy to read.
 Oh nevermind, I understand.. the colors indicate a block of lines that relate to a single comment. I think that would be clearer if the color didn't break between every line. It's still tricky mousing over things though. If you go straight down from one line to the next, the comment doesn't change. You have to mvoe away from the text entirely, then back onto the line you're interested in.
I think its an awesome concept and I'm glad someone is spending time building it
I like how you can do nested comments. The problem is it's not easy to see which comment goes where (I think you can just add a color code to the comments to indicate which color the comment is in response to.)
Great work, I think you can turn it into a real product.
So it's like github gist, but with annotations. Sometimes I post codes with annotations on my site.
Of course, Japanese has its own writing system, and "click" is written as クリック and pronounced roughly as "kurikku").
Nice idea though!
(Harmless alert popup)
Aren't those code comments?
- Currate the results on the frontpage a little? It's filled with test posts
- Group & filter (e.g. on language)
- IMHO this is extra valuable in smallish groups. So some functionality to "facilitate" that would be great :)
And a URL structure like http://kurikku.com/user/hello-world would look nifty in my opinion.
If you can get this as a plugin into eclipse, xCode and code sharing sites like stackoverflow you have your $100M startup.
I think that's the good idea though, we lack a way to aggregate every information we have on a line of particular code. More comments will be valuable.
Yes, but with some minor differences. In Github you have a very narrow window to comment on a line of code, think in a withstanding pull request, before it gets merged, after that the code is kinda all set. This in my opinion has a lot of potential and I would love to help if there is a way.
I would like to see the ability to search by language by clicking on the [language] part of headers though. Also maybe being able to view annotations by user.
But github and team features are definitely planned for the future if people like it.
I think you need some prominent and excellent "hero" examples of what you'd like to see on the site. Pick something reasonably pithy (e.g. off the top of my head Pike's simplified regex implementation) and annotate it and make that the top link (or one of the top links)
all login and registration pages MUST run under https