[OT] Go officially won't get generics
Bruno Medeiros via Digitalmars-d
digitalmars-d at puremagic.com
Fri May 9 04:38:10 PDT 2014
On 08/05/2014 22:09, Bienlein wrote:
> On Wednesday, 7 May 2014 at 15:54:42 UTC, Paulo Pinto wrote:
>> So the videos of the Gophercon 2014 are being made available.
>>
>> Rob Pike did the keynote. At the expected question about generics,
>> his answer was "There are no plans for generics. I said we're going to
>> leave the language; we're done.".
>>
>> Discussion ongoing on HN,
>>
>> https://news.ycombinator.com/item?id=7708904
>>
>> --
>> Paulo
>
> I agree with Paulo. At 54:40 he says what Paulo has already quoted. And
> "we are done" means "that's it, folks". It even sounds to me like the
> language is finished and it will be left like that.
>
> -- Bienlein
I find this aspect much more interesting than the "get generics or not"
one. So Rob Pike and the other guy is leaving the language then?
I wonder what that means for the future of Go. I guess the community
will take over, but will there be someone from Google still in charge?
And how many resources/manpower from Google will they still dedicate to Go?
The thing about generics is that, if Go where to break through and
become a mainstream popular language, generics would likely be added to
it somehow. Maybe in the main language, as in Go 2.0, or maybe as
side-project/language-extension (Go++ ?) that someone else would take.
Similar to Java which tried to keep the language as simple as possible
in the beginning (no operator overload, no metaprogramming or generics,
etc), but eventually saw the shortcoming as too significant.. (even if
the only thing they added was type-parameterization generics, but even
just that makes a big difference)
--
Bruno Medeiros
https://twitter.com/brunodomedeiros
More information about the Digitalmars-d
mailing list