down because
"It would be too hard to explain the code to someone".
That says to me that it is crappy code that the developer (one
guy) does not want to document.
Crappy code should be *fixed*, not documented, BTW. ;-)
it should be both fixed AND documented
Which is why I
got into defining XAP. Help design XAP, then a good
Fruity clone on top of it.
Yeah. And speaking of which, what's going on ATM?
I'm speccing. The mess of changes to the header were losing too much
detail, so I am writing the spec first :) Hopefully will have a Table of
Contents and draft this weekend.
Anyway, I've been thinking about XAP and this
Unified effort. A few
facts, assumptions and questions:
What I'm saying is basically that we have nothing
to lose, and
possibly a lot to win.
Agreed 100%.
Tim