Maybe it is better to use a function that wasn't implemented in the latest nodejs, but differs in iojs. Therefore, we may have a chance to show the new user the difference.

That's a good idea, maybe place that in the resources for new users section?

My thoughts were to keep it short and simple just to test if the build was working.

To throw my coals onto the fire, I'd love to see a nodejs.org-like example with an HTTP server rather than a CLI-evaluated line. It doesn't have too much relevance to this PR specifically but it has more value to me than just "Hello".

@brendanashworth I can probably take a tackle at that, but wouldn't that go in a place in the docs and not just the readme? If there's a place I can do that for sure, I'd be glad to do it.

On another note, I seem to be having trouble getting ES6 working in my terminal/command line on both OSX and Windows. Is this a known issue, or did I just set it up wrong?

@jimmyhsu I always liked how the nodejs.org example was easy to follow and kind of "in the spotlight", so I'd like to have it in the readme, but its more of a trivial thing.

Regarding ES6, I'd say open an issue, if it turns out its an error on your end or a known issue (that I don't know about) we can always close it.

@jimmyhsu looks good! tiny nit: can you rebase the PR against master, squash it to one commit and prefix it with the section you are editing (in this case doc:)? The first line of the description should be not longer than 50 chars (more details at https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#step-3-commit)

thank you!

can you rebase the PR against master

Did you mean v1.x? Master is months behind.

@bnoordhuis ah thanks yes, meant v1.x

@robertkowalski Sounds good! I'll tackle this later in the week and dig a bit more into why ES6 isn't working quite right.

ping @jimmyhsu

$ iojs -p process.version

We can use that for testing the build, but I think an actual example should be more thorough.

LGTM. Landed in 54d5437.