The State of Go

Where we are in June 2014

Andrew Gerrand

Yesterday

Initial reception

Looking back on the first months.

Complaints

The complaints started right away…

Familiar complaints

Familiar complaints

The first HN thread about Go was mostly an argument about braces and indentation.

Historic moments

The first public language change (Dec 10, 2009):

The gopher

The gopher

The gopher

A keen observation

Signs of hope

Today

Growth

User groups

Today there are 48 active user groups in 15 countries across 5 continents.

GopherCon

Community-driven. 3 days. 700 attendees. 24 talks. 1 panel. 4 hours of lightning talks!

The gopher

The gopher

The gopher

Go 1.3

Released last Wednesday, 18 June 2014.

Highlights:

Tomorrow

Upcoming conferences

Go 1.4

Due December 1st, 2014.

What might be in it? (Speculative list follows.)

New language features

Nope.

Canonical import paths

A means for a repository to specify its canonical import path.

Goal: stop people from checking out repos from the wrong path.

Applications:

"camlistore.org" -> "camlistore.googlesource.com/camlistore"

(Proposal forthcoming.)

Internal packages

Current proposal:

"An import of a path containing the element “internal” is disallowed if the importing code is outside the tree rooted at the parent of the “internal” directory."

And, later:

src/pkg → src

Move the standard library from $GOROOT/src/pkg to $GOROOT/src.

Basically makes $GOROOT work just like $GOPATH.

(Not a big deal for most, but a nice clean up for the core.)

File system access throttling

Throttling of access to the file system at the os package level.

Goal:

Make it work just as nicely as it does with the network.

(Proposal forthcoming.)

"go generate"

A convenience for generating Go source code. Example uses:

Proposed mechanism:

Add generator directive in Go source files:

//go:generate yacc -o gopher.go gopher.y

Use the Go tool to execute the directives:

% go generate [packagepath]

(Proposal forthcoming.)

More tool chain work

The transition from C to Go continues:

Better GC and malloc

Rough estimate: 10-20% overall speedup, 20-50% GC pause reduction, 5-10% RSS reduction.

Details:

Other runtime changes

Concurrency improvements:

C to Go:

Package changes

Ports

Go support for Android

Go support for the NDK. (Like C/C++ today, but better!)

Goal: enough support for writing games.

Based on the work of Elias Naur and others in the community.

More

Questions?

演讲者

Andrew Gerrand