Personally, I do not fear to change the comment implementation later. That's what Smalltalk is good at.
But that doesn't mean it's the right choice :) The thing is that we can go full speed with this and make comments for: oneLineSummary longDescription usageDescription preInstallComment postInstallComment authorshipText contactDescription creationDate lastUpdateDate and a long etcetera Or we could go beyond this and define set of properties, each one with it's priority to be shown and some way to define the order of rendering. Problem is: where to draw the line? My initial strategy was to have comments and then model the commonalities of all package comments away to the appropiate method/variable/data Let's keep discussing this.
