Live data from Hacker News

Go 1.14

blog.golang.org

1–10 of 26 posts

Re: Go 1.14

#2
A rather nice ~10% speed boost for my tool scc from this just with a simple recompile against some input sets.

    $ hyperfine 'scc' './scc'
    Benchmark #1: scc
      Time (mean ± σ):      43.5 ms ±   1.7 ms    [User: 30.4 ms, System: 88.2 ms]
      Range (min … max):    40.5 ms …  48.9 ms

    Benchmark #2: ./scc
      Time (mean ± σ):      39.6 ms ±   1.3 ms    [User: 46.1 ms, System: 89.7 ms]
      Range (min … max):    35.9 ms …  42.5 ms

    Summary
      './scc' ran
        1.10 ± 0.06 times faster than 'scc'
Trying it on various other inputs it seems to be somewhere between 3% and 10%

I am surprised they are still getting these sort of gains to be honest. From memory 1.13 for the same workload came with a ~3% improvement over 1.12. This is purely in terms of wall clock time to run the same code over the same inputs. Have not had a look at the impact of a long running process or memory yet.

Re: Go 1.14

#3
I love Go. It’s too bad that go modules broke ide support and godocs. I miss the simplicity of gopath.

Edit:

Go modules were not welcomed and godep was supposed to be the official dep manager: https://twitter.com/_rsc/status/1022588289461743617

Godoc is broken because of it and Rob Pike doesn't like it: https://github.com/golang/go/issues/26827#issuecomment-51584...

VScode with gomodules is still bad even with gopls restarting every 20m: https://github.com/Microsoft/vscode-go/wiki/Go-modules-suppo...

Re: Go 1.14

#5

I love Go. It’s too bad that go modules broke ide support and godocs. I miss the simplicity of gopath. Edit: Go modules were not welcomed and godep was supposed to be the official dep manager: https://twitter.com/_rsc/status/1022588289461743617 Godoc is broken because of it and Rob Pike doesn't like it: https://github.com/golang/go/issues/26827#issuecomment-51584... VScode with gomodules is still bad even with gopls…

it made it painful for a while, but GoLand and VSCode both support modules at this point (though VSCode uses the gopls[1] (language server), that I've been having mixed results with).

[1] https://github.com/golang/tools/tree/master/gopls

Re: Go 1.14

#6

I love Go. It’s too bad that go modules broke ide support and godocs. I miss the simplicity of gopath. Edit: Go modules were not welcomed and godep was supposed to be the official dep manager: https://twitter.com/_rsc/status/1022588289461743617 Godoc is broken because of it and Rob Pike doesn't like it: https://github.com/golang/go/issues/26827#issuecomment-51584... VScode with gomodules is still bad even with gopls…

Hello,

I'm new to go (and so far enjoying it). I haven't use modules yet. How do they break IDE support ? (using Goland here)

Re: Go 1.14

#7
Thanks to the Go team for the great work!

The more I use it, the more I enjoy Go. Having grown up with the healthy dose of Pascal and later Modula 2, I appreciate many traits of Go which let me just focus on the tasks at hand. With very little "magic" going on, some parts of the code might be a bit tedious, but you also always have the feeling of being in control, as everything is very explicit. Add to that a few underapreciated dynamic features. I am first of all a professional Lisp/Scheme programmer and a lot of Scheme concepts translate surprisingly well into Go due to having first class functions and a garbage collector.

It is very nice to see how the Go releases are very careful to add new features while continuosly improve on the "quality" side. Enhancing the performance of "defer" is a great example. Like unwind-protect in Lisp, it is a very elegant way to ensure that cleanup code is run under any circumstance. Removing its overhead is a big thing.

Re: Go 1.14

#8

I love Go. It’s too bad that go modules broke ide support and godocs. I miss the simplicity of gopath. Edit: Go modules were not welcomed and godep was supposed to be the official dep manager: https://twitter.com/_rsc/status/1022588289461743617 Godoc is broken because of it and Rob Pike doesn't like it: https://github.com/golang/go/issues/26827#issuecomment-51584... VScode with gomodules is still bad even with gopls…

I constantly see this sentiment and don't get it. It's perfectly fine in GoLand, and has been for the year I've been using it. What's broken for you?

Re: Go 1.14

#9
post #6

I love Go. It’s too bad that go modules broke ide support and godocs. I miss the simplicity of gopath. Edit: Go modules were not welcomed and godep was supposed to be the official dep manager: https://twitter.com/_rsc/status/1022588289461743617 Godoc is broken because of it and Rob Pike doesn't like it: https://github.com/golang/go/issues/26827#issuecomment-51584... VScode with gomodules is still bad even with gopls…

Hello, I'm new to go (and so far enjoying it). I haven't use modules yet. How do they break IDE support ? (using Goland here)

It doesn't. You just need to configure goland properly

Re: Go 1.14

#10
post #6

I love Go. It’s too bad that go modules broke ide support and godocs. I miss the simplicity of gopath. Edit: Go modules were not welcomed and godep was supposed to be the official dep manager: https://twitter.com/_rsc/status/1022588289461743617 Godoc is broken because of it and Rob Pike doesn't like it: https://github.com/golang/go/issues/26827#issuecomment-51584... VScode with gomodules is still bad even with gopls…

Hello, I'm new to go (and so far enjoying it). I haven't use modules yet. How do they break IDE support ? (using Goland here)

I haven't used Goland but vscode is broken.
Post reply on HN