Live data from Hacker News

Go 2, here we come

blog.golang.org

51–60 of 534 posts

Re: Go 2, here we come

#51

I haven't been keeping up with Go much these days but is there proper debugger support now? Or is it still a half-broken experience?

If you use Goland 2018 it's pretty seamless, there are a few things missing like being able to get ptr addresses and view values in hex, and it's a little laggy compared to VS but not bad.

Re: Go 2, here we come

#53
> We are constrained by the fact that we now have millions of Go programmers and a large body of Go code

Are there really "millions" (plural) of Go programmers?

Sounds like a bit of an overestimate, no?

Re: Go 2, here we come

#54
post #26

I tried Go a while ago. I was hooked by the performance , the community around it and vendors support ( AWS , Heroku , GCloud etc...) but I got quickly fed up by the awkward package management system, the weird syntax and the horrible idea of $GOPATH, especially on Windows. Haven’t tried it since. Hope lots of this change to make the language more welcoming for Newcomers to the language.

Actually, the issues you mention are already fixed by Go modules.

EDIT: Removed a parenthetical that was based on a misreading of the parent.

Re: Go 2, here we come

#55
post #34
post #27

I’m hoping that https://github.com/golang/go/issues/19623 will come through, and we’ll get a native “true integer” type (and hopefully a rational one as well, though maybe this is pushing it a bit). This is really something that should be implemented at the language level, so that “int” can become a true integer, yet still remain efficient in many cases. It is bizarre to me that languages boasting built-in language-l…

This was one thing COBOL got right: built in support for a DECIMAL data type.

Don't be stupid. A "decimal" type is a floating-point number, just with a different base. It solves none of the underlying problems.

(Which is why, incidentally, nothing made in this millennium supports it.)

Re: Go 2, here we come

#57
post #54
post #26

I tried Go a while ago. I was hooked by the performance , the community around it and vendors support ( AWS , Heroku , GCloud etc...) but I got quickly fed up by the awkward package management system, the weird syntax and the horrible idea of $GOPATH, especially on Windows. Haven’t tried it since. Hope lots of this change to make the language more welcoming for Newcomers to the language.

Actually, the issues you mention are already fixed by Go modules. EDIT: Removed a parenthetical that was based on a misreading of the parent.

I believe they’re saying that vendor support is a good thing in Golang.

Re: Go 2, here we come

#59
post #6

I'll be very sad if this goes the way of Perl 6

Honestly that would be great if it took the momentum out of Go and killed the language. I loathe working in Go.

Then don't, but actively wanting to see something gone that other enjoy is beyond tasteless.

Re: Go 2, here we come

#60
post #26

I tried Go a while ago. I was hooked by the performance , the community around it and vendors support ( AWS , Heroku , GCloud etc...) but I got quickly fed up by the awkward package management system, the weird syntax and the horrible idea of $GOPATH, especially on Windows. Haven’t tried it since. Hope lots of this change to make the language more welcoming for Newcomers to the language.

You might like Rust. It has a much better story in these areas.
Post reply on HN