Andrei's list of barriers to D adoption

[Walter Bright via Digitalmars-d]

On 6/7/2016 12:01 PM, Adam D. Ruppe wrote:
> the key point: the default behavior means apathy ruins the feature. Use a library
> written by someone who didn't care to write @nogc, but nevertheless didn't
> actually use the gc? too bad.

I don't think it is that bad. Lots of formerly acceptable C coding practice is 
still perfectly allowed by the C Standard, but has become laughed at in 
practice, such as:

   #define BEGIN {
   #define END }

The point being that a culture of "best practices" does arise and evolve over 
time, and professional programmers know it. Such has also arisen for D over 
things like unittests and Ddoc comments. Would you even want to use a library 
not written by professionals who have a reasonable awareness of best practices? 
Would you want to use a library where the maintainers refuse to use @nogc even 
if they aren't using the gc?