Andrei's list of barriers to D adoption

[Atila Neves via Digitalmars-d]

On Monday, 6 June 2016 at 19:43:13 UTC, qznc wrote:
> On Monday, 6 June 2016 at 02:20:52 UTC, Walter Bright wrote:
>> * Hiring people who know D is a problem.
>>
>> * Documentation and tutorials are weak.
>>
>> * There's no web services framework (by this time many folks 
>> know of D, but of those a shockingly small fraction has even 
>> heard of vibe.d). I have strongly argued with Sönke to bundle 
>> vibe.d with dmd over one year ago, and also in this forum. 
>> There wasn't enough interest.
>
> All three of those are affected by documentation and tutorials. 
> From this list, this seems to be the biggest issue.
>
> Personally, this is surprising to me. I have read lots of 
> complaints here in the forum, but I never experienced it 
> myself. I think my first contact with D was in 2009 or 2010 and 
> the documentation was certainly not better then. My conclusion 
> is that I'm not normal. This also means I have a hard time to 
> see where it should be improved.

Same here. I'm perfectly fine with the tools and docs as they are 
now, they wouldn't make my top 20 priorities. It's a common 
complaint, and therefore this must be important for other people, 
but I just don't get it. Conversely, Go is usually brought up as 
an example of a language with good tools. I've written some Go 
and I also don't understand what people mean when they say that. 
Why are they good? What's easier?

This thread itself has had multiple people say that Phobos lacks 
proper examples of usage, which is the exact opposite of what I'd 
say. I'd rather have runnable documentation (unit tests) than 
static-could-be-lying-cos-it-hasn't-been-updated docs any day of 
the week and twice on Sundays.

I read TDPL cover-to-cover in an afternoon, started writing code 
and never looked back. Conclusion? I'm weird.

Atila