D vs Go in real life

[SomeDude]

On Thursday, 21 November 2013 at 09:33:04 UTC, Bienlein wrote:
> What puzzles me is the enormous activity in the Go forum. Only
> the Python forum has that much traffic. It seems to me that
> people are all that happy if they have a language with which 
> they
> can just start hacking around on something.
>
> That is because Go doesn't force anyone to think about design.
> The only design-level construct it has is the class an that's 
> it.
> Embedding is truly only to save coding effort not having to type
> in dereferenciation chains as in C. There is nothing except
> classes, but no inheritance, traits, mixins, overriding, etc. So
> there is nothing that forces you to think about your design in
> Go. And you don't have to know about manual memory management as
> in Rust.
>
> -- Bienlein

That actually makes it a good first language to learn programming 
(and also bad programming). Simplicity is appealing. A language 
that can be learnt in a couple of afternoons is always pleasant 
and will draw masses. OTOH, if it doesn't force you to think 
about design, I guess the absence of design bites you in the long 
term. Then, the simplicity of the language added to the fact that 
it's statically typed might allow for fairly sophisticated 
refactoring using tooling.
These are just suppositions, I don't have any experience with Go.