Book Image

Mastering Go - Second Edition

By : Mihalis Tsoukalos
Book Image

Mastering Go - Second Edition

By: Mihalis Tsoukalos

Overview of this book

Often referred to (incorrectly) as Golang, Go is the high-performance systems language of the future. Mastering Go, Second Edition helps you become a productive expert Go programmer, building and improving on the groundbreaking first edition. Mastering Go, Second Edition shows how to put Go to work on real production systems. For programmers who already know the Go language basics, this book provides examples, patterns, and clear explanations to help you deeply understand Go’s capabilities and apply them in your programming work. The book covers the nuances of Go, with in-depth guides on types and structures, packages, concurrency, network programming, compiler design, optimization, and more. Each chapter ends with exercises and resources to fully embed your new knowledge. This second edition includes a completely new chapter on machine learning in Go, guiding you from the foundation statistics techniques through simple regression and clustering to classification, neural networks, and anomaly detection. Other chapters are expanded to cover using Go with Docker and Kubernetes, Git, WebAssembly, JSON, and more. If you take the Go programming language seriously, the second edition of this book is an essential guide on expert techniques.
Table of Contents (20 chapters)
Title Page

Programming UNIX pipes in Go

According to the UNIX philosophy, UNIX command-line utilities should do one job and perform that job well. In practice, this means that instead of developing huge utilities that do lots of jobs, you should develop multiple smaller programs, which, when combined, should perform the desired job. The most common way for two or more UNIX command-line utilities to communicate is by using pipes. In a UNIX pipe, the output of a command-line utility becomes the input of another command-line utility. This process may involve more than two programs. The symbol that is used for UNIX pipes is the | character.

Pipes have two serious limitations: firstly, they usually communicate in one direction, and secondly, they can only be used between processes that have a common ancestor. The general idea behind the implementation of UNIX pipes is that if you do not have a...