I wonder whether/how-best to apply our principle of minimalism when it applies to areas of the system that, while critical, seem inherently non-minimalist e.g. test harnesses, documentation, etc.
I thought a lot about this when trying to document and refactor SDL. The lack of a mock library in core was a big barrier to understanding the interactions between SDL objects. Maybe I'm being naive, but I feel like if someone wants a minimal image, they're not going to want to load SUnit or rich text documentation *at all*, so I don't see the risk-benefit of crippling these features. This also applies to Pillar/Microdown. While *any* rich text comments are an exciting development, I'd like to understand the benefit of Microdown vs. full Pillar syntax. Presumably the primary benefit is the size of the codebase. Any other reasons? A few other questions about the "rich text doc" roadmap: 1. Could/will this be extended to method comments? That would be really cool :) 2. How close are we for someone to use full Pillar syntax in class comments in their own library? Any plans to make this possible? NB. I originally posted a version of this on an older thread about Pillar but and I'm assuming it may have gotten lost in that limited context. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
