WingNews logo WingNews GitHub [2]
top | item 17574140

Go 1.11 Beta 2 is Released

118 points| melzarei | 7 years ago |groups.google.com

70 comments

order
[+] dcu|7 years ago|reply
This beta includes experimental support for modules (also known as vgo)

if you're interested, there's a series of articles explaining how modules work here: https://research.swtch.com/vgo

[+] Cthulhu_|7 years ago|reply
And here's someone's experiences with it: https://github.com/Vandebron/Vandebron/pull/2532

Getting started with a Go project is now easier and faster - install go runtime, clone, run a command to install dependencies, build & run. No more need for a go specific file structure (although I guess it'll still help if you're doing professional development)

[+] Lio|7 years ago|reply
WebAssembly is a really interesting feature for me.

I'll be interested to find out more about interactivity with the rest of the javascript world via syscall/js.

[+] hartz|7 years ago|reply
I'm also excited to see where this leads.

From the release notes:

> Go programs currently compile to one WebAssembly module that includes the Go runtime for goroutine scheduling, garbage collection, maps, etc. As a result, the resulting size is at minimum around 2 MB, or 500 KB compressed.

The minimum size is a bit unfortunate, but after all it is still just experimental.

[+] jedisct1|7 years ago|reply
Go binaries not running any more on Windows < 7 is going to be a serious issue.
[+] rhencke|7 years ago|reply
As far as I know, not even Microsoft supports Windows versions below 7 anymore. Vista support has ended, and XP support ended long ago.
[+] coldtea|7 years ago|reply
>Windows < 7 is going to be a serious issue

Because people deploy Go on Windows? And what's more, on Windows < 7?

(And they also need to be able to recompile with the very latest Go?)

[+] kxkfkkfvv|7 years ago|reply
How so? You can still compile with go 1.10
[+] ValentineC|7 years ago|reply
I personally think Go binaries not being supported on macOS 10.9 and earlier is a bigger issue, though the absolute market size is definitely smaller.

bradfitz of the Go team did mention in an earlier thread [1] that this mainly means that they won't be testing on those older OSes.

[1] https://news.ycombinator.com/item?id=16395242

[+] PopsiclePete|7 years ago|reply
People still stupid enough to run Windows XP are the real issue here, not Go. Those people need to be quickly isolated on their own little island of stupidity and cordoned/blocked off from the rest of the human population on Earth, ASAP.
[+] redcat255|7 years ago|reply
I wonder, is there a chance for go to ever become a paid language?
[+] mseepgood|7 years ago|reply
I get paid for writing Go at my job.
[+] nkozyra|7 years ago|reply
As in ... pay to use it? That concept seems like a relic at this point, no?
[+] phito|7 years ago|reply
It will come with generics
[+] quantumwoke|7 years ago|reply
I am disappointed every time I see a new Go release and go to check the release notes. The language is still lacking features like generics, sane concurrency primitives and even performance in some cases. Of course the WebAssembly port in 1.11 is an impressive feat of engineering, but I can't see myself replacing core components at my company with Go yet. Fingers crossed.
[+] mseepgood|7 years ago|reply
If you check each Go release notes for generics you're doing it wrong. If generics will come one day you will have heard about it long before any release notes.
[+] endorphone|7 years ago|reply
It sounds like other languages fill your needs better. That's okay, different languages target different philosophies and needs.
[+] ancarda|7 years ago|reply
>sane concurrency primitives

Could you elaborate on this? Are you perhaps talking about STM? I can't think of anything else that is really missing.

[+] pjmlp|7 years ago|reply
If you think Go will ever get generics you are fooling yourself.