On Sat, 06 Apr 2013 18:10:26 +0100, Marcus Denker <[email protected]>
wrote:
I'm also not attempting to say that those who are very active with
Pharo are bad programmers because documentation has become
problematical - if they are then I'm a bad programmer too - I just want
to point out that a system has even more need of documentation than a
completed application and *if it's possible* (and I know that finance
is an issue in the real world) then I think that updating the Pharo
book(s) to a point where they describe the current Pharo 2.0 state is
FAR more important than work on Pharo 3.0.
We need both. Documentation is important, but just documenting a system
that nobody needs makes no sense, either.
I would agree. I don't think that Pharo2.0 counts as a system that nobody
needs, though. I'm paid to develop for Moodle, a vast PHP-based e-learning
project and I can assure you that the world is full of people who need a
proper OO development system!
Obviously there's a balance to be had, but I don't think that it's too
radical to suggest that a major version bump should be followed by a
period of consolidation in the documentation before proceeding.
TW
