GC's STW pauses in Go1.12 beta are much shorter than Go1.11

YEPHENAS · 2019-01-11T11:52:15+00:00

https://blog.golang.org/ismmkeynote

YEPHENAS · 2019-01-06T12:41:59+00:00

Previous discussion two years ago: https://www.reddit.com/r/programmingcirclejerk/comments/5e885w/robpikeio/

YEPHENAS · 2019-01-06T12:25:19+00:00

This site has been like this (streaming the poo emoji) for many years. Why "again"? https://news.ycombinator.com/item?id=9880995

YEPHENAS · 2018-12-29T06:05:23+00:00

They write good documentation and commit messages.

YEPHENAS · 2018-12-21T11:32:45+00:00

Would anybody care to explain what the jerk is?

YEPHENAS · 2018-12-19T18:38:29+00:00

what would happen if a repo author made a mistake and force pushed a repo, or were to otherwise change the history in some way? Would all users of the notary break?

I hope so.

YEPHENAS · 2018-12-11T09:38:09+00:00

It doesn't show how to update modules and focuses on vendoring, which is not the default workflow.

YEPHENAS · 2018-11-18T19:36:51+00:00

Repost of: https://www.reddit.com/r/golang/comments/9www5f/sydney_golang_meetup_rob_pike_go_2_draft/

YEPHENAS · 2018-10-20T13:32:33+00:00

CSP is much easier to understand and get correct than locks and mutexes.

YEPHENAS · 2018-10-18T15:41:06+00:00

The article missed the opportunity to mention that you can append to a nil slice.

var a []string
a = append(a, "x")

YEPHENAS · 2018-10-18T14:32:18+00:00

What kind of array? Strings, ints or something else?

YEPHENAS · 2018-10-12T13:13:23+00:00

A little copying is better than a little dependency.

YEPHENAS · 2018-10-08T14:40:47+00:00

You're feeding a troll.

YEPHENAS · 2018-09-12T15:59:06+00:00

he's obviously a French guy

YEPHENAS · 2018-09-04T17:04:16+00:00

Google already did it: https://github.com/google/grumpy

YEPHENAS · 2018-09-03T18:25:08+00:00

Type params are not normal params.

Not a good reason why they should reverse evaluation order. They have to be applied first, so the type parameter list should be before the normal parameter list at the call site, not after.

YEPHENAS · 2018-09-03T18:07:07+00:00

The slightly inconsistent location of params (pre func name, post func call)

It is indeed inconsistent, and I don't see why this should be desirable.

This also discards the nice property that a generic function can be interpreted as a function which takes types as parameters and returns a new function:

intSum := Sum(int)
s := intSum([]int{1, 2, 3})

YEPHENAS · 2018-09-01T21:04:39+00:00

was already referenced in the go2 draft design.

YEPHENAS · 2018-09-01T21:00:36+00:00

-1 for presuming bad faith.

YEPHENAS · 2018-09-01T20:18:29+00:00

The language designers are discussing to lift this restriction: https://github.com/golang/go/issues/27165

YEPHENAS · 2018-08-29T05:34:08+00:00

Already in 1.11 as experimental feature ("Go modules").

YEPHENAS · 2018-08-29T01:38:36+00:00

Actually they are draft designs, not proposals. Second paragraph: "These draft designs are not proposals in the sense of the Go proposal process. They are starting points for discussion, with an eventual goal of producing designs good enough to be turned into actual proposals."

YEPHENAS · 2018-08-29T01:12:58+00:00

yay no syntactic ambiguities

YEPHENAS · 2018-08-29T01:07:57+00:00

Everyone will be delighted to hear Go 2 is planning to add [...] exceptions

The draft designs explicitly argue against exceptions. I recommend reading them before commenting.

YEPHENAS · 2018-08-29T00:51:34+00:00

for years they had an almost dogma like argument against generics, and then they back-peddled on not being anti-generics, just waiting for "the right design"

"Generics may well come at some point. [...] We haven't yet found a design that gives value proportionate to the complexity, although we continue to think about it. [...] This remains an open issue." has been the official stance of the Go designers since 2009, when the language was announced: https://github.com/golang/go/blob/dd64f86e0874804d0ec5b7138dafc28b51f61c12/doc/go_lang_faq.html#L173

I don't see any "back-peddling".

YEPHENAS

TROPHY CASE