Go 2, here we come
blog.golang.org
Go 2, here we come
1–10 of 534 posts
Re: Go 2, here we come
#2Go 2 Considered Harmful:
https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.p...
Re: Go 2, here we come
#3Rob Pike had a good talk on the Go 2 process and a few of the proposals that went up on YouTube a few days ago:
Re: Go 2, here we come
#4Big fan of both Go and also Rust. It is time we move beyond C and C++
Re: Go 2, here we come
#5Go 2 Considered Harmful: https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.p...
You got me. Genuinely thought it was gonna be a critique.
Re: Go 2, here we come
#6I'll be very sad if this goes the way of Perl 6
Re: Go 2, here we come
#7I hope they keep the changes reasonable and do not introduce any breaking changes. I like the language as it is now and I'm very productive in it.
Re: Go 2, here we come
#8> Go 2 will be much more community-driven.
Please no ...
Re: Go 2, here we come
#9Well I must say the Go team is certainly putting in the work to avoid a catastrophic major version bump (e.g. Python).
That said, any major additive change to Go, especially generics and/or try/catch will push me away from the language. If I need a well designed language, I have Rust. Go's sell for me is it's so naively simplistic it's actually useful when your team members are idiots.
If they bolt on type variables, well that's just a different language, and we'll just end up on the hedonistic treadmill towards another Java. No thank you.
Re: Go 2, here we come
#10Non-go user here. So what are the most desired fratures from Go 2 in the community?
I remember something about generics not being supported.