A few notes on choosing between Go and D for a quick project

[Israel via Digitalmars-d]

On Monday, 16 March 2015 at 01:22:47 UTC, cym13 wrote:
>
> HINT 2: it took me about a month and a good tutorial on 
> templates (btw, thanks G.Willoughby) to start understanding the 
> full prototypes of standard functions. I really recommend 
> putting the constraint part in slight grey so that it is still 
> here and readable but the immediatly useful part of the 
> prototype stands out.
>
> HINT 3: no beginner cares about how exactly it is compiled or 
> advanced metaprogramming options. This should not be more than 
> mentionned in a "getting started" page. It is cool stuff, it 
> should be said, but it definitely does not fit in an 
> introduction to any language.

Its hard to get this across but i too would like to see a simpler 
and easier to understand tutorial on D rather than seeing all 
these complicated things. Even Ahlis book isnt that great. Its 
good, but not great.

> HINT 4: D is great. It is a good language already. Stop 
> mutating it! Fix bugs, improve the standard library, work on 
> the ecosystem, reduce compile-time, but do not try breaking 
> things all the time. Don't even think of improving yield as I 
> suggested before, I'd prefer a standard library based solution 
> at this point.

You definitely have a point. The problem is that everyone else 
see's D as an open source community driven language so everyone 
and their mother wants to contribute their own features, stuff 
like this is bound to happen.
This could also be a bad thing because if D falls behind on its 
bleeding edge mutation it could cause a collapse on people being 
interested.