Channels ▼

Web Development

Google Is Go For "Go 1" Open Source Language

Search giant Google has used its developer blog and coding portal to detail the formal arrival of its Go open source programming language, which this week has reached version 1. First initiated back in November 2009, the Go project has enjoyed contributions from more than 200 programmers who have between them input code, tests, and documentation.

Go 1 is the first release of Go that is available in supported binary distributions. They are available for Linux, FreeBSD, Mac OS X, and Windows.

Google's Scott Knaster has explained that the Go programming language (and its set of core libraries) version 1 will be affectionately known as Go 1 for short. The Go team has reportedly spent "months of work" refining the specification, improving the implementation, increasing portability, and reworking and adjusting the standard library.

Google says that code that compiles in Go 1 should, with just a few exceptions, continue to compile and run throughout the lifetime of that version, even as the company issues updates and bug fixes (such as Go version 1.1, 1.2, and so on).

According to Knaster, "Go 1 introduces changes to the language (such as new types for Unicode characters and errors) and the standard library (such as the new time package and renamings in the strconv package). Also, the package hierarchy has been rearranged to group related items together, such as moving the networking facilities, for instance the rpc package, into subdirectories of net. A complete list of changes is documented in the Go 1 release notes. That document is an essential reference for programmers migrating code from earlier versions of Go."

"We also restructured the Go tool suite around the new go command, a program for fetching, building, installing, and maintaining Go code. The go command eliminates the need for Makefiles to write Go code because it uses the Go program source itself to derive the build instructions. No more build scripts!"

This language release also sets in motion a new release of the Google App Engine SDK — the company explains that a similar process of revision and stabilization has been applied to the App Engine libraries, thus providing (in theory) a base for developers to build programs for App Engine that will run for years.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.