What are the differences between shells?

That is a great question! While all shells are designed to interpret your commands and pass them to the Linux kernel, they differ in their features, syntax, and purpose.

Here is a breakdown of the most common shells you will encounter:

1. sh (Bourne Shell)

• The Ancestor: Developed by Stephen Bourne at Bell Labs in the 1970s.
• Pros: It is the "lowest common denominator." It exists on almost every Unix-like system ever made.
• Cons: Very limited. It lacks features we take for granted today, like arrow-key history, tab-completion, or advanced aliases.
• Use Case: Writing simple, highly portable system scripts.

2. bash (Bourne-Again Shell)

• The Standard: A modern replacement for sh and the default shell for most Linux distributions (including the one you are using now).
• Pros:
  • Tab-completion: (Autocomplete commands/files).
  • History: You can press the up arrow to see old commands.
  • Configuration: Highly customizable via the .bashrc file.
• Use Case: Interactive daily use and general-purpose scripting.

3. dash (Debian Almquist Shell)

• The Specialist: You might see this on Ubuntu or Debian.
• Purpose: It is much smaller and faster to load than Bash.
• Use Case: On many systems, /bin/sh is actually a symbolic link to dash. It’s used to run system boot scripts as fast as possible, but it is not intended for humans to type in (interactive use).

4. zsh (Z Shell)

• The Powerhouse: The default shell on macOS and popular among developers.
• Pros: Includes everything Bash has, plus:
  • Better spelling correction (e.g., if you type sl instead of ls).
  • Advanced "theming" (like the famous "Oh My Zsh" framework).
  • Shared history across different terminal windows.
• Use Case: Power users who want a beautiful and highly productive interface.

5. fish (Friendly Interactive Shell)

• The Modernist: Designed to be "user-friendly" right out of the box without any configuration.
• Pros: Autosuggestions (it predicts what you want to type in grey text) and web-based configuration.
• Cons: It is not POSIX-compliant, meaning scripts written for sh or bash might not work in fish.
• Use Case: Users who want a great experience without editing config files.

Summary Table

In this lab, changing joker to bash is a big "quality of life" improvement, as it makes the terminal much easier for a human to use! Which one sounds most interesting to you?