News for hackers. Stuff that matters.
Re:How a programming language documentation ought to look li... by regularfry on Friday November 19, 2010 @04:32PM (#1922877)
Python's docs lack a place for comments, which is a shame.
Re:How a programming language documentation ought to look li... by codefisher on Friday November 19, 2010 @04:52PM (#1922944)
It would just turn into a place where nobs ask questions, and you really want that done in the proper place. And you also have the moderator overhead.
Re:How a programming language documentation ought to look li... by regularfry on Saturday November 20, 2010 @04:57AM (#1924224)
The classic example of where this actually works well is in the PHP docs. Yes, you get idiots, but you also get good, real-world examples of a wider variety than the original documentation authors would have been able to produce. It's about the only thing I missed when I jumped from PHP to Python.

I think the Django Book's approach to this is really good as well, where the moderator overhead is implicitly taken on by the documentation authors. That works for them because they treat the document as a project in itself, rather than as a by-product.

Re:How a programming language documentation ought to look li... by forsaken on Friday November 19, 2010 @04:47PM (#1922926)
Your bug is my feature.