Why was ApacheWiki implemented using the particular breed of wiki?
- It only took 5 minutes to set up.
Discussion on which wiki had no possible conclusion any more than "Which is the OneTrueLanguage: Common Lisp, Java, PERL, PHP, Python, C, or Ada?"
- It takes very low resources
- It takes like NO administration
- It just uses the filesystem.
- Less is more.
- Why didn't we use some other wiki
- It probably would have taken more than 5 minutes to set up.
- This is the only wiki Andy has ever used (because it serves his purpose and didn't require him to think real hard about it)
- It most likely would have taken more resources
- It more than likely would have required some administration
- It more than likely would have required more than just the filesystem
- You didn't get off your butt and do it, and Andy got impatient
- More is less
Why isn't it in Java/PHP/Python or whatever the OneTrueLanguage is?
- Because Andy doesn't care what technology his tools are in as long as they work.
- What about feature X and Y and bla bla bla?
I think (as usual) some folks are missing the ball here. Generally when discussion turns to documentation, everyone starts talking about how to enhance the tool, versus actually generating documentation. CVS *gasp* sucks, and it sucks pretty bad, but folks haven't stopped coding until we have the *perfect revision control system*. However if you insist then consider contributing actual work... WikiProjectPage.
For what it's worth, I think UseModWiki is the best choice all around, based on my experience. The most popular wiki, WikiPedia, started with UseModWiki and went a long way with it until it splintered into its own independent version. Adding new features (via patches) to UseModWiki is pretty easy and rewarding too.