2 types of D users, both can live together happily if we adjust

[Vic via Digitalmars-d]

I completely understand and support the DIY nature of Open Source 
and it's something that should be underlined often!

If we turn out to be successful, I  do plan to resource out D 
support. But I'm running a startup and don't have the spare 
cycles. But I am using D, betting the company on it, programmers 
in my shop do D 100% of time, so I do consider myself a part of 
the D community.
So all I can do is wish for a small and stable D lang, vs a large 
D experimental platform - and both are possible. If I had 
resources I would divide Phobos and complier/pre-compiler to 
support the 2 camps: people that use D on real projects and 
people that want to experiment as I have outlined.
I do think this to be key thing for the active D community to 
internalize as it relates to D wide adoption or disappearing: the 
size of project managed as it releases to FTE (~2000 hrs/year) 
resources that maintain it. Manifested mostly as 
http://en.wikipedia.org/wiki/Feature_creep or instability (is my 
code wrong or is it D )


On Thursday, 27 November 2014 at 23:24:59 UTC, H. S. Teoh via 
Digitalmars-d wrote:
> On Thu, Nov 27, 2014 at 10:58:31PM +0000, Vic via Digitalmars-d 
> wrote:
>> There are 2 users I see, those that see it as an experimental 
>> feature
>> platform and those that use it for real projects (and not for
>> experiments).
> [...]
>
> The thing is, based on my observations over the past few years 
> or so
> I've been here, such grand plans have often been proposed (in 
> the best
> of intentions, to be sure) but rarely carried out. The thing 
> about D is
> that if you wish to see something happen, you just have to dig 
> in and
> *do* something about it. Be the champion of whatever you 
> propose, get on
> the ground and work it out, make it happen. Contribute code. 
> Help
> improve the infrastructure. Be the change you wish to see take 
> place.
>
> While these forums can be quite entertaining, from my 
> observations most
> of the animated discourse ultimately results in nothing -- 
> because
> nobody actually got up to *do* something about it. The stuff 
> that *does*
> happen often happens in the background where somebody actually 
> did the
> hard work and wrote the code, pushed the PR's through to 
> acceptance,
> contributed the hardware to improve the infrastructure, etc., 
> often with
> little or no activity on the forums.  Almost all of the 
> discussions on
> the forums that have little or no code backing it up tend to 
> just
> sputter out after everyone's energy has been exhausted, and 
> nothing
> happens.
>
> So, if you wish to see the changes you propose, I'd say your 
> best bet is
> to start *doing* something about it (besides talking about it 
> on the
> forum, that is). Remember that this is an open source project 
> with
> contributions made by volunteers; telling volunteers what to do 
> with
> their free time rarely works. Contributing real work, OTOH, 
> tends to
> catch people's attention much more effectively.
>
>
> T