aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Gerrand <adg@golang.org>2015-11-10 15:06:31 +1100
committerAndrew Gerrand <adg@golang.org>2015-11-10 04:40:39 +0000
commitfec215f0025573dd72bd7158cecbd5f43e57d9a6 (patch)
tree6165bb5b05b0670af50943b62869a384da5ba1eb
parent22a4f219543ff5e2f8c396be4c40abc441bc587b (diff)
content: amendements to "Six years" article
Change-Id: If2287bb751322c59a3582c008158f4b4580cedaa Reviewed-on: https://go-review.googlesource.com/16757 Reviewed-by: Ian Lance Taylor <iant@golang.org> Reviewed-by: Alan Donovan <adonovan@google.com>
-rw-r--r--content/6years.article22
1 files changed, 11 insertions, 11 deletions
diff --git a/content/6years.article b/content/6years.article
index 10b6bb7..5617d78 100644
--- a/content/6years.article
+++ b/content/6years.article
@@ -8,9 +8,9 @@ adg@golang.org
Six years ago today the Go language was released as an open source project.
Since then, more than 780 contributors have made over 30,000 commits to the
-project's 22 repositories. The open source ecosystem is still growing, with
-GitHub reporting more than 90,000 Go repositories.
-And, offline, more Go events and user groups continue to pop up
+project's 22 repositories. The ecosystem is still growing, with GitHub
+reporting more than 90,000 Go repositories.
+And, offline, new Go events and user groups continue to pop up
[[https://blog.golang.org/gophercon2015][around]]
[[http://blog.golang.org/gouk15][the]]
[[http://blog.golang.org/gopherchina][world]].
@@ -20,16 +20,16 @@ And, offline, more Go events and user groups continue to pop up
In August we [[https://blog.golang.org/go1.5][released Go 1.5]], the most
significant release since Go 1. It features a completely
[[https://golang.org/doc/go1.5#gc][redesigned garbage collector]] that makes
-the language more suitable for latency-sensitive applications, marks the
+the language more suitable for latency-sensitive applications; it marks the
transition from a C-based compiler tool chain to one
-[[https://golang.org/doc/go1.5#c][written entirely in Go]], and also includes
-ports to [[https://golang.org/doc/go1.5#ports][new architectures]], notably
-better support for ARM processors (the chips that power most smartphones).
+[[https://golang.org/doc/go1.5#c][written entirely in Go]]; and it includes
+ports to [[https://golang.org/doc/go1.5#ports][new architectures]], with better
+support for ARM processors (the chips that power most smartphones).
These improvements make Go better suited to a broader range of tasks, a trend
that we hope will continue over the coming years.
-We also continued to boost developer productivity through better tools, with
-the introduction of the [[https://golang.org/cmd/trace/][execution tracer]] and the
+Improvements to tools continue to boost developer productivity.
+We introduced the [[https://golang.org/cmd/trace/][execution tracer]] and the
"[[https://golang.org/cmd/go/#hdr-Show_documentation_for_package_or_symbol][go doc]]"
command, as well as more enhancements to our various
[[https://talks.golang.org/2014/static-analysis.slide][static analysis tools]].
@@ -39,7 +39,7 @@ with better support for other editors in the pipeline.
Early next year we will release more improvements in Go 1.6, including HTTP/2
support for [[https://golang.org/pkg/net/http/][net/http]] servers and clients,
-an official package vendoring approach, support for blocks in text and HTML
+an official package vendoring mechanism, support for blocks in text and HTML
templates, a memory sanitizer that checks both Go and C/C++ code, and the usual
assortment of other improvements and fixes.
@@ -47,5 +47,5 @@ This is sixth time we have had the pleasure of writing a birthday blog post for
Go, and we would not be doing it if not for the wonderful and passionate people
in our community. The Go team would like to thank everyone who has contributed
code, written an open source library, authored a blog post, helped a new
-gopher, or just given Go a try. Without you Go would not be as complete,
+gopher, or just given Go a try. Without you, Go would not be as complete,
useful, or successful as it is today. Thank you, and celebrate!