Switch documentation to using iojs by default

[taoeffect]

https://www.debian.org/releases/jessie/amd64/release-notes/ch-information.en.html#libv8

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/12658854-switch-documentation-to-using-iojs-by-default?utm_campaign=plugin&utm_content=tracker%2F528702&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F528702&utm_medium=issues&utm_source=github).

[SGrondin]

Maybe I'm not understanding the issue correctly, but wouldn't a better solution be to compile from source against the latest release instead of relying on a (relatively) unproven project that is moving at neck-breaking speed?

[taoeffect]

@SGrondin Compile NodeJS from source? I don't think most people will want to do that. iojs is at least moving. :P

They also have some sort of package thing setup for various platforms (ppa mechanism or whatnot). So we can defer to that in our docs. It's best to use a project is is receiving security updates than one that's not.

[Svenskunganka]

Node.js and io.js is getting merged soon. See Node Foundation, so we can probably hold on a little while until that happens.