3 ms·
This article got me thinking a little. I know base pretty well; whenever I'm writing some code, I always end up hitting the "source code" link and checking out
by jrockway 16y ago
This article got me thinking a little. I know base pretty well; whenever I'm writing some code, I always end up hitting the "source code" link and checking out the implementation. I never really wonder "how does this work" as I'm programming anymore.
The question is, how can one go from knowing a library to contributing to the library? One of the problems with HackageDB is that you can see everything, but you can't see where you can make changes.
I had a problem with C2HS a few months or so ago; it didn't work on Windows (because DLLs use "stdcall", not "ccall", and the "ccall" string was hard-coded). I clicked the darcs link on Hackage to get the source. Dead. So I just edited the source on my local machine and moved on.
A few months later I noticed that darcs was working again and there was a new maintainer, and I did get to contribute my patch. But it was kind of dumb luck, I could have easily had never noticed, and this bug never would have been fixed.
So right now, it's easy to find libraries, it's easy to understand libraries, but it's not always easy to improve the libraries. And incidentally, the biggest problem with libraries in Haskell is that they never get out of the "rough draft" stage, by getting contributions from people other than the author.
Incidentally, I don't have this problem with Perl, because everyone happens to use Github. This has created an interesting effect where libraries that aren't on Github become very difficult to work on, and people seem to favor rewriting instead of fixing things "the old way". (diff + an email to the author.)