You are polluting Your Standard Output ( stdout ) in Go

Using fmt.Println for error handling isnt a practical way, especially in linux or unix based systems.

because if you're using bash or zsh or any other shell, there will be 3 types of file descriptors, stdout, stderr, and stdin (which are low level integer table numbers that the kernel assign them for each communication channel )

when logging erros with fmt.Println you're polluting your Standard output data stream ( stdout ( 1 ) ) which might be used for CLI driven utility or similar, and using print() or println() isnt ideal for production grade, because both of them redirect every output to stderr amd both are almost temporary built in functions for fast debugging/bootstrapping that might get removed

Here is the show case :

package main

Using fmt.Println for error handling isnt a practical way, especially in linux or unix based systems.

Here is the show case :

package main

You are polluting Your Standard Output ( stdout ) in Go

You are polluting Your Standard Output ( stdout ) in Go

Related reading

Debugging Go With Delve: Beyond fmt.Println

printf() and scanf() in C: Understanding Input and Output

Why using strconv instead of fmt for converting typical data types to string

Go Error Handling: Annoying or Awesome?

Error Handling — Learning to Love `if err != nil`

🐍 Flask Python Structured Logging — What Most Miss in Production

Related reading

Debugging Go With Delve: Beyond fmt.Println

printf() and scanf() in C: Understanding Input and Output

Why using strconv instead of fmt for converting typical data types to string

Go Error Handling: Annoying or Awesome?

Error Handling — Learning to Love `if err != nil`

🐍 Flask Python Structured Logging — What Most Miss in Production