A strategic vision for D

[Joakim]

On Wednesday, 2 May 2018 at 03:44:37 UTC, Nick Sabalausky 
(Abscissa) wrote:
> On 05/01/2018 10:27 PM, Joakim wrote:
>> 
>> Those are specific technical priorities that hint at a 
>> strategy, as you say, but it is better to lay out that 
>> strategy itself. Not knocking that vision document, as I 
>> called for a concrete document like that for years, but a 
>> conference keynote is a good place to lay out a strategy too.
>
> I think the "overall strategy" is simply: "Identify the most 
> important things for the core folk to work on, prioritize those 
> things." Really don't think anything beyond that really matters 
> or exists. We're not exactly pitching to VC's here.

Yes, but how is it decided what the "most important things" are? 
There is a strategy at work for any prioritization, even if it's 
implicit and never even articulated in their own minds. If 
unarticulated, you can gain a lot by spending time to articulate 
it, as you may find unwanted contradictions in the way you had 
been prioritizing.

As for pitching VCs, there's a reason they want to know that 
vision, to know if that's something worth investing in. 
Similarly, potential D users and the existing community want to 
know if there's a vision worth investing their time and money 
into.

Since D is an open source project, they're always free to ignore 
the core team's vision and use D in their own way, ie meld their 
own vision as Linus talks about happened with linux over the 
years, but it helps to know what the core team's strategy is for 
many people.