Overview - Bash vs other shells (Zsh, Fish, sh)

What is it?

A shell is a program that lets you talk to your computer by typing commands. Bash, Zsh, Fish, and sh are different types of shells, each with its own features and ways of understanding commands. Bash is the most common shell on many systems, while Zsh and Fish offer more user-friendly features. Sh is a simpler, older shell often used for basic scripting.

Why it matters

Different shells make using the command line easier or harder depending on what you need. Without these shells, you would have to interact with your computer in a much more complicated way. Choosing the right shell can save time, reduce errors, and make your work more enjoyable and efficient.

Where it fits

Before learning about different shells, you should understand what a shell is and basic command line usage. After this, you can explore scripting in each shell and advanced features like customization and automation.

Mental Model

Core Idea

A shell is like a translator between you and your computer, and different shells offer different languages and tools to make communication easier or more powerful.

Think of it like...

Imagine you have different types of translators for a foreign language: one is simple and direct (sh), another is popular and reliable (Bash), and others add helpful hints and shortcuts (Zsh and Fish) to make conversations smoother.

┌─────────────┐
│   User      │
└─────┬───────┘
      │ Types commands
┌─────▼───────┐
│   Shell     │
│ (Bash/Zsh/  │
│  Fish/sh)   │
└─────┬───────┘
      │ Translates commands
┌─────▼───────┐
│ Operating   │
│ System      │
└─────────────┘

Build-Up - 7 Steps

1

FoundationWhat is a Shell and Its Role

Concept: Introduce the basic idea of a shell as a command interpreter.

A shell is a program that reads what you type and tells the computer what to do. It lets you run programs, manage files, and automate tasks by typing commands. Without a shell, you would need to use a graphical interface or other tools to control your computer.

Result

You understand that a shell is the bridge between you and your computer's operating system.

Understanding the shell's role is key to knowing why different shells exist and how they affect your interaction with the computer.

2

FoundationIntroducing Bash, Zsh, Fish, and sh

3

IntermediateComparing Syntax and Features

4

IntermediateCustomization and User Experience

5

AdvancedCompatibility and Portability Considerations

6

ExpertInternal Architecture and Performance Differences

7

ExpertAdvanced Scripting and Ecosystem Integration

Under the Hood

Shells read your typed commands, parse them into instructions, and pass them to the operating system to execute. They manage environment variables, handle input/output redirection, and control script flow. Differences in parsing rules, built-in commands, and extensions define each shell's behavior and capabilities.

Why designed this way?

Shells evolved to balance simplicity, compatibility, and user convenience. Sh was designed for basic scripting and portability. Bash extended sh with more features for interactive use. Zsh added even more user-friendly features and customization. Fish focused on modern usability with smart defaults and visual aids. Each design reflects trade-offs between power, ease, and compatibility.

┌───────────────┐
│ User Input    │
└──────┬────────┘
       │
┌──────▼────────┐
│ Shell Parser  │
│ (syntax check)│
└──────┬────────┘
       │
┌──────▼────────┐
│ Command Exec  │
│ (built-ins &  │
│ external cmds)│
└──────┬────────┘
       │
┌──────▼────────┐
│ Operating Sys │
│ Kernel        │
└───────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Do you think Fish shell scripts run exactly like Bash scripts? Commit to yes or no.

Common Belief:Fish shell scripts are the same as Bash scripts and can run without changes.

Tap to reveal reality

Quick: Do you think Bash is always the fastest shell for running scripts? Commit to yes or no.

Common Belief:Bash is the fastest shell because it is the most common.

Tap to reveal reality

Quick: Do you think all shells support the same customization options out of the box? Commit to yes or no.

Common Belief:All shells offer the same level of prompt customization and user aids by default.

Tap to reveal reality

Quick: Do you think sh is obsolete and no longer used? Commit to yes or no.

Common Belief:Sh is outdated and replaced by Bash and others everywhere.

Tap to reveal reality

Expert Zone

1

Zsh's advanced globbing and array handling can simplify complex scripts but are often overlooked.

2

Fish's design sacrifices POSIX compatibility for user-friendliness, which can surprise experienced shell users.

3

Bash's compatibility mode with sh is imperfect; some scripts behave differently depending on invocation.

When NOT to use

Avoid Fish for scripts that must run on many systems without Fish installed; prefer sh or Bash for portability. Avoid Bash for minimal embedded systems where sh is lighter. Avoid Zsh if your environment lacks it or for scripts requiring strict POSIX compliance.

Production Patterns

Use Bash for most Linux server scripts due to its balance of features and availability. Use Zsh for developer workstations to improve interactive use. Use Fish for beginners or users valuing ease of use. Use sh for system startup scripts and maximum portability.

Connections

POSIX Standard

Bash, Zsh, and sh relate to POSIX as a standard for shell behavior and scripting compatibility.

Understanding POSIX helps grasp why sh scripts run almost everywhere and why Bash and Zsh add features beyond this standard.

User Interface Design

Fish shell emphasizes user-friendly design principles similar to modern UI/UX approaches.

Knowing UI design concepts explains why Fish prioritizes helpful prompts and visual feedback, improving command line usability.

Natural Language Translation

Shells act like translators converting human commands into machine instructions, similar to language translation systems.

This connection highlights the importance of syntax and semantics in shells, just as in human languages.

Common Pitfalls

#1Writing a script in Bash syntax but running it with sh, causing errors.

Wrong approach:#!/bin/sh for i in {1..5}; do echo $i; done

Correct approach:#!/bin/bash for i in {1..5}; do echo $i; done

Root cause:sh does not support Bash-specific syntax like brace expansion, leading to script failure.

#2Assuming Fish shell scripts can be run by Bash without changes.

Wrong approach:#!/usr/bin/env bash set -g theme_nerd_fonts yes

Correct approach:#!/usr/bin/env fish set -g theme_nerd_fonts yes

Root cause:Fish uses different commands and syntax; running Fish scripts in Bash causes errors.

#3Expecting all shells to have the same prompt customization by default.

Wrong approach:Using Bash without configuring PS1 and expecting colorful prompts and autosuggestions.

Correct approach:Install and configure Oh My Zsh or Fish shell for advanced prompt features out of the box.

Root cause:Bash requires manual setup for advanced features, unlike Zsh and Fish which provide them by default.

Key Takeaways

Shells are command interpreters that let you communicate with your computer using text commands.

Bash, Zsh, Fish, and sh differ in syntax, features, customization, and compatibility.

Choosing the right shell depends on your needs: portability, user experience, or scripting power.

Scripts may not work across shells without adjustments due to syntax differences.

Understanding shell internals and ecosystems helps you write better scripts and choose the best tools.