Why Importing packages in Go? - Purpose & Use Cases

The Big Idea

What if you could skip writing boring code and use ready-made tools instead?

The Scenario

Imagine you want to build a Go program that needs to read files, work with dates, and print messages. Without importing packages, you'd have to write all that code yourself from scratch every time.

The Problem

Writing everything manually is slow and tiring. You might make mistakes, and it takes a lot of time to test and fix your own versions of common tools like reading files or formatting dates.

The Solution

Importing packages lets you reuse ready-made, tested code. You just tell Go which packages you want, and you get powerful tools instantly, saving time and avoiding errors.

Before vs After

✗ Before

func readFile() string { /* lots of code to open and read file */ }
func main() {
  content := readFile()
  fmt.Println(content)
}

✓ After

package main

import "fmt"
import "os"

func main() {
  content, _ := os.ReadFile("file.txt")
  fmt.Println(string(content))
}

What It Enables

Importing packages unlocks the power to build complex programs quickly by standing on the shoulders of others' work.

Real Life Example

When making a web server in Go, you import the net/http package to handle requests instead of writing all the networking code yourself.

Key Takeaways

Manual coding of common tasks is slow and error-prone.

Importing packages gives you tested tools instantly.

This saves time and lets you focus on your program's unique parts.