Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Go 1.13 Release Notes

golang.org

Post reply on HN
Print view View original

211–220 of 264 posts

Re: Go 1.13 Release Notes

#211

Post by tapirl »

LanceH wrote: post #172
littlestymaar wrote: post #53

Earlier quoted context omitted.

> a better C, aimed at server-side data plumbing I agree with all what you said but this. Go isn't a better C, it's a better Java.

I went to a Go meetup where I use Go as a complement to Ruby. The speaker and most of the others there were using it as a more expressive/easier C. The middle ground it has carved out seems to let everyone say that their language does something better, but there seems to be a good chance that Go does a reasonable job at what their language doesn't do well (and isn't too far off to learn).

it is a better-java language with c blood.

Re: Go 1.13 Release Notes

#212

Post by Cthulhu_ »

rolleiflex wrote: post #9
gameswithgo wrote: post #2

I like the way Go proceeds as a language, with features added very very slowly and the compiler and tools regularly improving. I hope Rust can settle down into a similar focus soon.

I think Go is the only software release at this point to whose releases I respond with ‘Ooh shiny’ and not ‘Oh god’. I love the way they’re doing this — calm, collected, slow, and with ample heads up. At this point, I think we all have some JavaScript PTSD.

Yeah, for me the turnaround point for JS was when they added classes - JS is not an oop language and trying to make it look like one doesn't work. Worse, they didn't even implement it properly - no access modifiers.

Call me a bit of a luddite but this is one of the reasons why I'm skeptical about generics in Go - it'll be another language construct to keep in mind. Mind you this opinion of mine is baseless because unfortunately I haven't had the opportunity to do any serious go development yet.

Re: Go 1.13 Release Notes

#213

Post by patrec »

cjensen wrote: post #175
skunkworker wrote: post #12

Earlier quoted context omitted.

It brought one of my favorite parts about writing numbers in languages such as Ruby over to Go. From 10000000 to 10_000_000 is such a readability improvement and should be no-cost.

You guys are going to make me cry again that C++ rejected using underscores in favor of... single-quote. O_o

Only someone with no typographic taste whatsoever would prefer 10_000 over 10'000, so personally I'll rather cry about only C++ getting this right.

Re: Go 1.13 Release Notes

#214

Post by tapirl »

donatj wrote: post #64

Contrary to what someone else has said, this is my least favorite release of Go ever. I'm salty about how the proxy, which is enabled by default, makes it so much more difficult to pull private modules by having to set environment variables on everyone's individual machines. I've got an issue being discussed on GitHub about it https://github.com/golang/go/issues/33985

go env -w GOPROXY=direct

go env -w GOSUMDB=off

Re: Go 1.13 Release Notes

#215

Post by Cthulhu_ »

littlestymaar wrote: post #53
bsaul wrote: post #49

Earlier quoted context omitted.

Rust can't settle down right now, because it still has to make necessary changes to critical parts of the language, such as async. Go always had a very narrow and precise ambition and scope (a better C, aimed at server-side data plumbing). Which is the reason why it was able to nail a set of features from the start and keep it that way. Rust has a much wider ambition : all the modern languages facilities (generics, m…

> a better C, aimed at server-side data plumbing I agree with all what you said but this. Go isn't a better C, it's a better Java.

Nah, Kotlin is a better Java, Go has a mostly different use case.

Re: Go 1.13 Release Notes

#216

Post by masklinn »

majewsky wrote: post #201
masklinn wrote: post #183

Earlier quoted context omitted.

> 1e7 Is a float literal.

Not in Go. Number literals don't have a type until they're assigned to a variable or used in a place that implies a type (e.g. a function argument). For example, the following is valid: var u uint32 = 10000000000.0 / 100000 even though 10000000000 overflows uint32 and it's also written like a floating-point literal.

> Not in Go.

Yes in go. `var u = 1e7` gives a float. That means 1e7 is a float literal. You can coerce it to an integer by explicitly typing the target, but it's still a float literal.

Re: Go 1.13 Release Notes

#217

Post by sjapkee »

sime2009 wrote: post #21

How does Go compare to Rust these days with respect to language maturity, community size and general maturity/availability of libraries? So far I've found Rust more interesting and pushes the envelope a bit more. But what is the sales pitch for Go?

Rust has no backward compatibility, a very disputable feature with language revisions when compiling, and it is rare for you to have a large package from a stable branch without loading the package from the test branch. So in its present form it looks interesting, but it is absolutely not adapted to use outside of pet projects.

Re: Go 1.13 Release Notes

#218

Post by arez »

Great so now we have a language that leaks my data to a proprietary service and I can't even see what they're doing with that data. Somehow Google becomes more and more like Microsoft was in the old days. Why is it so hard to not be evil? Why is it so hard for devs working at Google to use open-source paradigms and be careful with anything involving corporations? https://github.com/golang/go/issues/34029

Re: Go 1.13 Release Notes

#219

Post by rebolek »

patrec wrote: post #213
cjensen wrote: post #175

Earlier quoted context omitted.

You guys are going to make me cry again that C++ rejected using underscores in favor of... single-quote. O_o

Only someone with no typographic taste whatsoever would prefer 10_000 over 10'000, so personally I'll rather cry about only C++ getting this right.

Not only C++. Rebol and Red also get this right. And they also allow comma instead of a dot as a decimal separator, oh the horror!
Post reply on HN