Article discussing Go, could well be D

[Walter Bright]

On 6/8/2011 11:56 PM, Nick Sabalausky wrote:
> What you said above is also why I *strongly* believe that good (and I mean
> *good*) documentation is every bit as important as actually
> writing/releasing a tool or library in the first place. I've seen so much
> "already-made" work that's rendered barely-usable due to less-than-stellar
> documentation (or even worse: bad or non-existant documentation). What's the
> point out of putting stuff out there if nobody knows how to use it? What's
> the point of using something if figuring it out and getting it to work takes
> about as much effort as DIY? That's why (for public projects anyway) I force
> myself, even if I don't want to, to put all the effort I need to into
> documentation to make things as easy as possible. Otherwise, all that effort
> writing the code would likely have been for nothing anyway.


Sure. I struggle with writing documentation myself, and Ddoc has cut my effort 
involved in doing it by more than half. (I even use Ddoc to build Kindle ebooks, 
4 so far!)