Don't rant that long. Sometimes, documentation and code get out-of-synch for a lot of reasons.
- trying out stuff and documenting later. - plain forgetting to update the documentation. - having some stuff for a transition period, and then killing it. Your point that stuff that stays around, should ideally be documented, is a good point. Now, you gotta realize that people have limited time to do everything. In general, patches are welcome. In my long tenure on various tools, I've learnt that documenting stuff is always always a good idea: if you get a new feature BUT you can't explain it cleanly, then you should go back to the drawing-board !
