Hacker News Reader

> Why would anybody use a programming language with zero documentation for anything?

Why would you write documentation if your language implementation is still rapidly evolving?

Regardless, shouldn't you at least write documentation to isolate and identify confusing points of your rapidly evolving language? It's almost a matter of good practices; explaining something is usually the best way to learn it.

It depends. The language's author probably didn't post this, so who knows what stage of development his project is at.

You should write the documentation first. Otherwise what are you writing?

You're writing code for a purpose, obviously. Sometimes that purpose isn't clear from the outset, hence exploratory programming. So what would you be documenting at this point exactly?

Reply on news.ycombinator.com