Why I Like D

[forkit]

On Friday, 14 January 2022 at 02:13:48 UTC, H. S. Teoh wrote:
>
> How is using D "losing autonomy"?  Unlike Java, D does not 
> force you to use anything. You can write all-out GC code, you 
> can write @nogc code (slap it on main() and your entire program 
> will be guaranteed to be GC-free -- statically verified by the 
> compiler). You can write functional-style code, and, thanks to 
> metaprogramming, you can even use more obscure paradigms like 
> declarative programming.
>

I'm talking about the 'perception of autonomy' - which will 
differ between people. Actual autonomy does not, and cannot, 
exist.

I agree, that if a C++ programmer wants the autonomy of chosing 
between GC or not, in their code, then they really don't have 
that autonomy in C++ (well, of course they do actually - but some 
hoops need to be jumped through).

My point is, that a C#/Java programmer is more likely to be 
attracted to D, because D creates a perception of there being 
more autonomy (than that provided by C#/Java).

I'm not saying it's the only thing people consider. Obviously 
their choice is also reflected by the needs of their problem 
domain, their existing skill set, the skillset of those they work 
with, the tools they need, the extent to which their identity is 
attached to a language or community, etc..etc.

And I'm just talking about probability - that is, people are more 
likely to be attracted to something new, something that could 
benefit them, if it also enhances their perception of autonomy, 
or at least, does not not seek to diminish their existing 
autonomy (e.g a C programmer might well be attracted to betterC, 
for example).

D should really focus more on marketing one of its biggest 
strenghts - increased autonomy (well, the perception of).

Getting back to the subject of this thread, that's why 'I' like D.