If you just started learning Go, one thing will confuse you quickly:
👉 Arrays vs Slices
They look similar… but behave very differently.
Let’s break it down in the simplest way possible 👇
📦 What is an Array?
An array is a fixed-size collection.
numbers := [3]int{1, 2, 3}
Key points:
- Size is fixed
- Cannot grow or shrink
- Rarely used in real-world Go apps
🔄 What is a Slice?
A slice is a dynamic version of an array.
numbers := []int{1, 2, 3}
Key points:
- Size is dynamic
- Can grow using
append - Used almost everywhere in Go
⚡ Adding Data (Only Works with Slice)
numbers := []int{1, 2, 3}
numbers = append(numbers, 4)
Now:
[1, 2, 3, 4]
🧠 Under the Hood (Important Concept)
A slice is:
- Pointer to an array
- Length
- Capacity
Think of it like:
👉 “A flexible view on top of an array”
🔍 Slice Example with Capacity
numbers := make([]int, 2, 5)
fmt.Println(len(numbers)) // 2
fmt.Println(cap(numbers)) // 5
❗ Common Mistake
arr := [3]int{1,2,3}
arr = append(arr, 4) // ❌ ERROR
Why?
👉 Because arrays are fixed size
🔥 Real-World Use Case
When building APIs:
users := []string{}
users = append(users, "Ahmed")
users = append(users, "John")
Dynamic data = slices ✅
🧭 When to Use What?
| Feature | Array | Slice |
|---|---|---|
| Size | Fixed | Dynamic |
| Usage | Rare | Common |
| Flexibility | ❌ | ✅ |
👉 In 95% of cases → use slice
💬 Final Thought
If you understand slices, you understand how Go manages data internally.
This is a foundational concept—don’t skip it.
🚀 Coming Next
Next post:
👉 Structs in Go (this is where real backend modeling starts)
Top comments (0)