Hacker News new | ask | show | jobs
by hopeless 5362 days ago
The future's looking bright for Go.

I've recently been looking at some new languages: Scala, Haskell, Clojure, Node.js etc. Go was the only site to put code samples (live ones at that) on their front page.

Language/framework creators take note: The first thing I want to see on your site is what the code looks like. How to install it is a distant second (I can look it up once you've convinced me it's worth installing)

2 comments

I have never ever understood the desire to make installation details and lists of requirements the first thing I see on software docs. I come across all these tiny packages or full-blown applications and I have to literally spend minutes to figure out what they actually do.

Being open source is not a real advantage any more, but it takes so little effort to summarize your project at the top of the README, so please do it so I can fall in love with your stuff.

I've noticed that this problem exists even beyond software documentation. It's often hard to figure out what a company does by looking at their web site, for instance. I wish every such document started with "Product Foo is ____. It does ____."
I think that comes from the desire to find out if it's even worth exploring the project on a given hardware/software setup.

It may be a throwback, but it's still a good idea.

http://nodejs.org/ has a code sample.
You're right, I'd forgotten that one