Plan for D

[zjh]

D The biggest problem is that there is no direction.
Moreover, D author never confronts users' questions directly.
D needs to be organized and, at the same time, have a clear goal.
Let users, beginners, know what you're going to do.

However, the D authors and leading developers have never faced 
this problem.
If the user doesn't know what you're trying to accomplish, no 
matter how good the language,
The user had to leave. Because we don't know the solid point of 
your language.
What are you going to do? Are you going to match the user's 
expectations?
Can users see the improvement?
Yes, small progress is everywhere. But what we expect is your 
clear goals and steps.
C + + has 20, 23 and 26,
Rust, many companies are using. Go, even if itaims at junk 
template.
But what's D's goal? Do we have a schedule?

Is it true that we are doing things at random, and whoever has 
good things ,and then we will copy it?
Hope, D writers, wake up and make a schedule.
Let users see hope.