Why do you continue to use D?

[Dibyendu Majumdar]

On Saturday, 6 June 2020 at 01:17:02 UTC, Manu wrote:
> On Fri, Jun 5, 2020 at 3:30 AM Dibyendu Majumdar via 
> Digitalmars-d < digitalmars-d at puremagic.com> wrote:
>
>> On Friday, 5 June 2020 at 02:44:17 UTC, Manu wrote:
>>
>> > Back on-topic; I still use D because I just can't stand C++, 
>> > and I somehow fundamentally believe D can 'get there'... but 
>> > god is it a hard and frustrating road! Eternally so close, 
>> > but always juuuust misses the mark. Maybe one day we'll land 
>> > the shot >_<
>>
>> In my opinion there will always be that one missing feature 
>> that prevents D from getting there. In other words, if 
>> features were a stopping factor then how did anyone ever use 
>> C++ 10 years ago?
>>
>
> I feel like I made the case that it's not strictly 'features', 
> so much as implementation quality and/or the complete package 
> experience.
>

> So when I say "always just one thing", it's not features; it 
> might be...
> but it's often also implementation quality, or binary 
> environment
> integration issues, or build issues, or tooling issues... 
> unfortunately we
> must _exceed_ a very high bar set by the C++ to ecosystem be 
> successful.
> We're not evaluating which environment is the best experience 
> overall, what
> we have to do is *dislodge* a deeply seated establishment by 
> demonstrating
> sufficient advantages that it tips a subjective threshold of a 
> businesses
> technical directors. They need to do an evaluation, easily 
> recognise the
> advantages, and not be nervous.

In my opinion it's been to D's detriment that there is this ever 
present view that if only this particular feature was added, it 
would take D over the line...

But really what matters more in organizations is that can they 
depend on D to always work. It is far more important that all 
existing features work 100% reliably all the time.
And most organizations want good tooling support as well.

Regards