aboutsummaryrefslogtreecommitdiff
path: root/content/the-path-to-go-1.article
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2020-03-09 22:11:04 -0400
committerRuss Cox <rsc@golang.org>2020-03-11 14:10:08 +0000
commit482079d678d84e207dd9ae63266c4bd4e653886b (patch)
tree62aa3b630bbe982904f5495fe2cc53d60a87c92d /content/the-path-to-go-1.article
parent0b4fcd39865e575704b5928c9a8f1cd21e18e8b2 (diff)
content: wrap long lines using new program wrap.go
Wrapping long lines will make diffs easier to read for the eventual conversion to Markdown. For golang/go#33955. Change-Id: Ibcc1b5a84ccc9144b5fcdc9266f2da3e2cf3c5a3 Reviewed-on: https://go-review.googlesource.com/c/blog/+/222839 Reviewed-by: Ian Lance Taylor <iant@golang.org>
Diffstat (limited to 'content/the-path-to-go-1.article')
-rw-r--r--content/the-path-to-go-1.article13
1 files changed, 11 insertions, 2 deletions
diff --git a/content/the-path-to-go-1.article b/content/the-path-to-go-1.article
index 345cf93..1bb1f5f 100644
--- a/content/the-path-to-go-1.article
+++ b/content/the-path-to-go-1.article
@@ -6,10 +6,19 @@ Andrew Gerrand
* Introduction
-In July 2012, Rob Pike and I presented a talk at OSCON titled _The_path_to_Go_1_. In it we explain how Go 1 came to be, and outline the process by which Go was refined and stabilized to become the clean, consistent programming environment that it is today. We present the major highlights of the release and discuss the details behind some specific libraries and tools.
+In July 2012, Rob Pike and I presented a talk at OSCON titled _The_path_to_Go_1_.
+In it we explain how Go 1 came to be, and outline the process by which Go
+was refined and stabilized to become the clean,
+consistent programming environment that it is today.
+We present the major highlights of the release and discuss the details behind
+some specific libraries and tools.
.iframe //www.youtube.com/embed/bj9T2c2Xk_s 309 550
The slides for the talk are [[https://talks.golang.org/2012/go1.slide][available here]].
-It's almost a year since we cut Go 1.0 and we are now busy preparing Go 1.1. The release will include performance improvements to the gc compiler, garbage collector, and goroutine scheduler, some standard library additions, and many bug fixes and other improvements. Stay tuned, as we hope to release Go 1.1 in the coming weeks.
+It's almost a year since we cut Go 1.0 and we are now busy preparing Go 1.1.
+The release will include performance improvements to the gc compiler,
+garbage collector, and goroutine scheduler,
+some standard library additions, and many bug fixes and other improvements.
+Stay tuned, as we hope to release Go 1.1 in the coming weeks.