[Haskell-cafe] Cal, Clojure, Groovy, Haskell, OCaml, etc.

Job Vranish jvranish at gmail.com
Tue Sep 29 16:12:48 EDT 2009

 Andrew Coppin <andrewcoppin at btinternet.com> wrote:

> how do we fix all this?

I think the key here is to reduce the cost of contribution to a minimum.
Make it as easy as possible to contribute an example, or to fill in some
missing documentation (and to find it later).

Cabal and hackage have made it very easy to contribute and fetch packages
and I think this is the primary reason why there are so many hackage
packages. We need to make it even easier to contribute documentation.

I think having some haddock/wiki system that allowed user contributions
which could be displayed alongside the official package dos and an easy way
for package maintainers to incorporate the user supplied documentation into
the official package documentation would be very helpful.

To sum up:
1.  Make it stupidly easy to contribute documentation, notes, comments,
2.  Make sure all of this good stuff can be easily accessed in one place.

- Job

On Tue, Sep 29, 2009 at 3:36 PM, Andrew Coppin
<andrewcoppin at btinternet.com>wrote:

> Tom Tobin wrote:
>> This.  As an experienced Pythonista but a beginning Haskeller, there
>> is *no way* I would have been able to wrap my head around the basics
>> of Haskell without the tutorage of Learn You A Haskell, Real World
>> Haskell, and various smaller tutorials scattered around the Haskell
>> wiki — but I still find the array of libraries confusing (just what
>> comes with GHC — I'm not even talking about Hackage here), since the
>> documentation seems to be quite terse compared to Python's docs.  I'm
>> getting better at reading the code directly, but I'm often at a loss
>> for what a particular library is good for in the first place.  The
>> library documentation seems to assume a mathematical or (advanced)
>> computer science background, and has no problem sending a reader off
>> to see a journal paper for details — not exactly friendly to those who
>> are trying their hardest to unlearn their imperative ways as it is.
>> ;-
> While some of the stuff that comes with GHC is quite well documented,
> others are highly under-documented. (As an exercise, go count how many
> module descriptions say "inspired by the paper by XXX at this URL"...)
> Admittedly, the System.IO module probably isn't the place to explain what a
> monad is and write a full tutorial on using them. However, look at (say)
> Control.Concurrent.STM.TVar. In my copy (GHC 6.10.3) it lacks even type
> signatures, let alone actual descriptions. Similarly, Parsec has some lovely
> external documentation (unfortunately as a single giant HTML page), but the
> Haddock stuff is bare.
> Now, the operative question (and I'm sure we've debated this one before)
> is: how do we fix all this?
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.haskell.org/pipermail/haskell-cafe/attachments/20090929/582f2f53/attachment.html

More information about the Haskell-Cafe mailing list