Book Image

Hands-On System Programming with Go

By : Alex Guerrieri
Book Image

Hands-On System Programming with Go

By: Alex Guerrieri

Overview of this book

System software and applications were largely created using low-level languages such as C or C++. Go is a modern language that combines simplicity, concurrency, and performance, making it a good alternative for building system applications for Linux and macOS. This Go book introduces Unix and systems programming to help you understand the components the OS has to offer, ranging from the kernel API to the filesystem. You'll then familiarize yourself with Go and its specifications. You'll also learn how to optimize input and output operations with files and streams of data, which are useful tools in building pseudo-terminal applications. You'll gain insights into how processes communicate with each other, and learn about processes and daemon control using signals, pipes, and exit codes. This book will also enable you to understand how to use network communication using various protocols, including TCP and HTTP. As you advance, you'll focus on Go's best feature - concurrency, which will help you handle communication with channels and goroutines, other concurrency tools to synchronize shared resources, and the context package to write elegant applications. By the end of this book, you will have learned how to build concurrent system applications using Go
Table of Contents (24 chapters)
Free Chapter
Section 1: An Introduction to System Programming and Go
Section 2: Advanced File I/O Operations
Section 3: Understanding Process Communication
Section 4: Deep Dive into Concurrency
Section 5: A Guide to Using Reflection and CGO

Chapter 5

  1. What's a stream?
    A stream is an abstraction that represents a generic flow of incoming or outgoing data.
  2. What interfaces abstract the incoming streams?
    The io.Reader interface is an abstraction for incoming streams.
  3. Which interface represents the outgoing streams?
    The io.Writer interface is an abstraction for outgoing streams.
  4. When should a byte reader be used? When should a string reader be used instead?
    A byte reader should be used when the raw data is a slice of bytes, while a string reader should be used with strings. Converting from one type of data to another causes a copy and is inconvenient.
  5. What's the difference between a string builder and a byte buffer?
    A byte buffer can be reused and overwritten. A string builder is used to create a string without a copy, so it uses a byte slice and converts it to a string without copying, using...