My First Steps in Go as a JavaScript Dev Moving to DevOps

I’ve recently decided to take the plunge into Go (Golang) as part of my journey into DevOps. Coming from a JavaScript background, I’ve been curious about Go’s simplicity, performance, and its growing popularity in the DevOps world. Today, I want to share my first steps, some observations, and a couple of questions that came up while writing my first Go program. fmt.Println("Hello, Go!"); Question 1: Is it considered good practice to use semicolons in Go, or should I avoid them unless necessary? What’s the community’s take on this? doubleQuoteString := "Hello Go!"; // This is a string singleQuoteString := 'G'; // This is a rune (Unicode code point) Question 2: Why does Go differentiate between single and double quotes? Is this design choice related to Go’s type system or performance optimizations? Code on Github: w3cdpass / GO-Devops My First Steps in Go as a JavaScript Dev Moving to DevOps "# GO-Devops" View on GitHub

Mar 9, 2025 - 08:12

I’ve recently decided to take the plunge into Go (Golang) as part of my journey into DevOps. Coming from a *JavaScript * background, I’ve been curious about Go’s simplicity, performance, and its growing popularity in the DevOps world. Today, I want to share my first steps, some observations, and a couple of questions that came up while writing my first Go program.

fmt.Println("Hello, Go!");

Question 1: Is it considered good practice to use semicolons in Go, or should I avoid them unless necessary? What’s the community’s take on this?

doubleQuoteString := "Hello Go!"; // This is a string singleQuoteString := 'G'; // This is a rune (Unicode code point)

Question 2: Why does Go differentiate between single and double quotes? Is this design choice related to Go’s type system or performance
optimizations?

Code on Github:

w3cdpass / GO-Devops

My First Steps in Go as a JavaScript Dev Moving to DevOps

"# GO-Devops"

View on GitHub