D vs Go in real life

[Bienlein]

> It does not work on my field, because my employer does 
> consulting for Fortune 500 companies usually multi-site with 
> off-shoring component, where the technology stack is given by 
> the customers themselves.
>
> So unless Scala,D, Go, ... are requested, they won't be used.

I'm out of the consulting business for quite a while now. Now I'm
an internal employee and have to put up with what the architects
decide. And my company is not a large organization. The CTO
things you need an architect and then your software development
is fine. The architect is good at drawing system diagrams and
theoretical things. He doesn't care about languages, would never
talk to some developer, neither would the CTO. If you want a
change to JDK8 within 2020 you have to explain to the architect
what a closure is and why it is beneficial. I think it will be
very hard ... The problem is in general that company internal
development is not on a good technical level. You have to work
for some startup or a good technical company such as Google,
Facebook, Apple, Yahoo, etc. Those guys are out of the league of
most "ordinary" developers. So it will be Java and something else
in your spare time. Not wanting to be fatalistic, but this is how
I see the situation.

-- Bienlein