D vs Go in real life

[Dicebot]

On Friday, 29 November 2013 at 08:35:58 UTC, Bienlein wrote:
> Could you just quickly describe what you mean by "being forced 
> to move
> lot of things to run-time"? I simply don't see what you are 
> refering to.

For example the dreaded generics issue. You can workaround it in 
many cases by using common polymorphic storage types but it 
costs. Or some applications of declarative programming in D - one 
can avoid using reflection and just move base data to runtime 
values but that requires to do processing during runtime.

In your Rectangular example the difference will start to appear 
when one wants to express a function that accepts any Rectangular 
type. As far as I know, in Go only option uses fat pointer. In D 
you can also express it as template constrain and thus can make 
more finely tuned design decision.