My choice to pick Go over D ( and Rust ), mostly non-technical

[Paulo Pinto]

On Tuesday, 8 December 2020 at 00:44:57 UTC, Ola Fosheim Grostad 
wrote:
> On Tuesday, 8 December 2020 at 00:01:21 UTC, aberba wrote:
>> On Sunday, 6 December 2020 at 19:37:31 UTC, random wrote:
>>> On Saturday, 5 December 2020 at 21:38:40 UTC, Daniel N wrote:
>>>>
>>>> But what I don't get is, why would anyone choose Go over C# 
>>>> for instance, it also has an excellent ecosystem but the 
>>>> language is actually decent unlike Go.
>>>
>>> Learn to implement basic data structures like in C? (no 
>>> generics 2020 wtf!)
>>>
>>> To use a weird way of duck typing in a typed language? 
>>> (interfaces and upcoming generics)
>>>
>>> I don't get it too. The language is hilariously bad imho^^.
>>
>> We tend to focus on the language itself too much. Project 
>> managers care about delivering results ASAP. So they'll go for 
>> something with a matured ecosystem of tools and packages...to 
>> get things done.
>
> Actually, I think there should be much more focus on fixing the 
> language and runtime. Go builds on experience with plan9, they 
> did not start from scratch. They had iterations that predate Go.

Go builds on the experience of Inferno and Limbo. Apparently 
people keep forgetting Plant 9 was just the middle stop station.

http://doc.cat-v.org/inferno/4th_edition/

http://www.vitanuova.com/inferno/

And Project Oberon as well, namely the Oberon-2 language 
revision, https://en.wikipedia.org/wiki/Oberon-2

The container devops world has made knowing Go a must have skill, 
regardless how we think about its design.