code review 58590043: go.talks: add "Towards Go 1.3" talk

go.talks: add "Towards Go 1.3" talk

[adg, 2014-02-05 09:52:54]

Hello dvyukov, r (cc: golang-dev@googlegroups.com),

I'd like you to review this change to
https://code.google.com/p/go.talks

[dvyukov, 2014-02-05 10:37:35]

https://codereview.appspot.com/58590043/diff/100001/2014/go1.3.slide
File 2014/go1.3.slide (right):

https://codereview.appspot.com/58590043/diff/100001/2014/go1.3.slide#newcode82
2014/go1.3.slide:82: - make contended synchronous channel operations faster (use
buffering!)
drop "use buffering!" :)

[dvyukov, 2014-02-05 10:37:47]

LGTM but wait for r

[adg, 2014-02-05 12:42:33]

https://codereview.appspot.com/58590043/diff/100001/2014/go1.3.slide
File 2014/go1.3.slide (right):

https://codereview.appspot.com/58590043/diff/100001/2014/go1.3.slide#newcode82
2014/go1.3.slide:82: - make contended synchronous channel operations faster (use
buffering!)
On 2014/02/05 10:37:35, dvyukov wrote:
> drop "use buffering!" :)

how did I leave that in?! :P

[josharian, 2014-02-05 18:25:32]

Nice summary.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide
File 2014/go1.3.slide (right):

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode53
2014/go1.3.slide:53: - increase page size to 8K (~10% GC pause time)
Here and the next few lines, maybe "(~10% less GC pause time)"? Matches
"faster"/"fewer"/"memory savings" below.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode261
2014/go1.3.slide:261: These benefits not so relevant anymore.
Perhaps: "Those benefits are not as relevant anymore."

[r, 2014-02-05 18:55:56]

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide
File 2014/go1.3.slide (right):

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode16
2014/go1.3.slide:16: (Six months after Go 1.2; released December 1, 2013.)
s/;/,/

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode19
2014/go1.3.slide:19: * A todo list
to-do

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode21
2014/go1.3.slide:21: After Go 1.2 the Go contributors compiled a TODO list:
to-do
(be consistent)

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode42
2014/go1.3.slide:42: Resolves the "hot split" problem.
Makes smaller initial stacks practical - more goroutines in the same space.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode116
2014/go1.3.slide:116: (eg, during garbage collection).
s/eg/e.g./ or better (why use latin?) /for example/

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode150
2014/go1.3.slide:150: SunOS: work in progress, on track for Go 1.3.
i thought it was solaris.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode163
2014/go1.3.slide:163: In Go 1.2, `go` `build` stats every dependant source file
to see whether they have changed.
yikes. dependEnt

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode193
2014/go1.3.slide:193: As an experiment, I build "hello, world" at the release
points for go 1.0. 1.1, and 1.2.
s/build/built/
it's my typo but still...

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode218
2014/go1.3.slide:218: but only one instance of the linker can load those
packages into an executable.
The packages can be compiled in parallel by independent runs of the compiler,
but the linking must be done by a single linker process after compilation is
complete.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode221
2014/go1.3.slide:221: because does more work than a typical linker.
s/does/it does/

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode261
2014/go1.3.slide:261: These benefits not so relevant anymore.
anymore is not a word. any more. or better: "now".

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode270
2014/go1.3.slide:270: - Go is more fun!
it's a better language! symbol tables become maps, for instance. packages
encourage modularity. maybe some work can be parallelized.

[ioe, 2014-02-05 19:29:18]

added the comment about *global* free list in order to avoid the confusion with
e.g. per-request memory pools.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide
File 2014/go1.3.slide (right):

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode113
2014/go1.3.slide:113: The `sync.Pool` type provides a general thread-safe free
list.
s/general thread-safe free list/general thread-safe global free list/

[adg, 2014-02-06 03:30:04]

PTAL

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide
File 2014/go1.3.slide (right):

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode16
2014/go1.3.slide:16: (Six months after Go 1.2; released December 1, 2013.)
On 2014/02/05 18:55:56, r wrote:
> s/;/,/

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode19
2014/go1.3.slide:19: * A todo list
On 2014/02/05 18:55:56, r wrote:
> to-do

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode21
2014/go1.3.slide:21: After Go 1.2 the Go contributors compiled a TODO list:
On 2014/02/05 18:55:56, r wrote:
> to-do
> (be consistent)

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode42
2014/go1.3.slide:42: Resolves the "hot split" problem.
On 2014/02/05 18:55:56, r wrote:
> Makes smaller initial stacks practical - more goroutines in the same space.

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode53
2014/go1.3.slide:53: - increase page size to 8K (~10% GC pause time)
On 2014/02/05 18:25:32, josharian wrote:
> Here and the next few lines, maybe "(~10% less GC pause time)"? Matches
> "faster"/"fewer"/"memory savings" below.

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode113
2014/go1.3.slide:113: The `sync.Pool` type provides a general thread-safe free
list.
On 2014/02/05 19:29:18, ioe wrote:
> s/general thread-safe free list/general thread-safe global free list/

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode116
2014/go1.3.slide:116: (eg, during garbage collection).
On 2014/02/05 18:55:56, r wrote:
> s/eg/e.g./ or better (why use latin?) /for example/

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode150
2014/go1.3.slide:150: SunOS: work in progress, on track for Go 1.3.
On 2014/02/05 18:55:56, r wrote:
> i thought it was solaris.

I don't even know anymore.
Changed it to solaris

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode163
2014/go1.3.slide:163: In Go 1.2, `go` `build` stats every dependant source file
to see whether they have changed.
On 2014/02/05 18:55:56, r wrote:
> yikes. dependEnt

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode193
2014/go1.3.slide:193: As an experiment, I build "hello, world" at the release
points for go 1.0. 1.1, and 1.2.
On 2014/02/05 18:55:56, r wrote:
> s/build/built/
> it's my typo but still...

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode218
2014/go1.3.slide:218: but only one instance of the linker can load those
packages into an executable.
On 2014/02/05 18:55:56, r wrote:
> The packages can be compiled in parallel by independent runs of the compiler,
> but the linking must be done by a single linker process after compilation is
> complete.

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode221
2014/go1.3.slide:221: because does more work than a typical linker.
On 2014/02/05 18:55:56, r wrote:
> s/does/it does/

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode261
2014/go1.3.slide:261: These benefits not so relevant anymore.
On 2014/02/05 18:25:32, josharian wrote:
> Perhaps: "Those benefits are not as relevant anymore."

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode261
2014/go1.3.slide:261: These benefits not so relevant anymore.
On 2014/02/05 18:55:56, r wrote:
> anymore is not a word. any more. or better: "now".

Done.

https://codereview.appspot.com/58590043/diff/120001/2014/go1.3.slide#newcode270
2014/go1.3.slide:270: - Go is more fun!
On 2014/02/05 18:55:56, r wrote:
> it's a better language! symbol tables become maps, for instance. packages
> encourage modularity. maybe some work can be parallelized.

Done.

[r, 2014-02-06 03:43:40]

LGTM

https://codereview.appspot.com/58590043/diff/140001/2014/go1.3.slide
File 2014/go1.3.slide (right):

https://codereview.appspot.com/58590043/diff/140001/2014/go1.3.slide#newcode57
2014/go1.3.slide:57: - smarter slice grow (2-20% less cpu)
s/cpu/CPU/ throughout

[nathany, 2014-02-06 04:44:14]

https://codereview.appspot.com/58590043/diff/140001/2014/go1.3.slide
File 2014/go1.3.slide (right):

https://codereview.appspot.com/58590043/diff/140001/2014/go1.3.slide#newcode176
2014/go1.3.slide:176: .link http://golang.org/cl/48310043
Just wanted to mention a draft API doc: http://goo.gl/MrYxyA

It's still really rough, so I'm not sure if it makes sense to link to yet.

[adg, 2014-02-06 04:56:48]

*** Submitted as
https://code.google.com/p/go/source/detail?r=5c1ef7ac81bc&repo=talks ***

go.talks: add "Towards Go 1.3" talk

LGTM=dvyukov, r
R=dvyukov, r, josharian, nightlyone, nj
CC=golang-codereviews, golang-dev
https://codereview.appspot.com/58590043

https://codereview.appspot.com/58590043/diff/140001/2014/go1.3.slide
File 2014/go1.3.slide (right):

https://codereview.appspot.com/58590043/diff/140001/2014/go1.3.slide#newcode57
2014/go1.3.slide:57: - smarter slice grow (2-20% less cpu)
On 2014/02/06 03:43:40, r wrote:
> s/cpu/CPU/ throughout

Done.

[adg, 2014-02-06 04:56:54]

On 6 February 2014 05:44, <nj@nathany.com> wrote:

> Just wanted to mention a draft API doc: http://goo.gl/MrYxyA
>
> It's still really rough, so I'm not sure if it makes sense to link to
> yet.
>

I ran out of space on the slide.

[nathany, 2014-02-06 05:03:26]

On 2014/02/06 04:56:54, adg wrote:
> On 6 February 2014 05:44, <mailto:nj@nathany.com> wrote:
> 
> > Just wanted to mention a draft API doc: http://goo.gl/MrYxyA
> >
> > It's still really rough, so I'm not sure if it makes sense to link to
> > yet.
> >
> 
> I ran out of space on the slide.

Not a problem.