The Magic Right Out of the Box
The first impression of fish is one of immediate satisfaction. Unlike traditional shells like Bash that often require extensive setup and plugins to feel modern, fish works beautifully from the start. Its most-praised feature is its intelligent autosuggestions.
As you type, fish displays a faint grey suggestion based on your history, which you can accept with a single keystroke. This, combined with syntax highlighting that colors commands to show you if they’re valid before you even hit enter, makes the terminal feel less like a guessing game and more like a conversation. It also boasts robust tab completion that doesn't just complete file paths, but also command options, often with helpful descriptions parsed directly from man pages. This out-of-the-box experience makes fish seem wonderfully simple because it anticipates your needs without asking you to configure a thing.
A Real Scripting Language Under the Hood
The simplicity of the interactive experience cleverly masks the fact that fish employs a completely different, and arguably more modern, scripting language than its predecessors. One of the biggest departures is its intentional lack of POSIX compliance. While this sounds like a drawback, it’s a deliberate design choice that allows fish to discard decades of accumulated quirks from shells like Bash. Instead of convoluted `if [ ... ]; then ... fi` blocks, fish uses a cleaner `if...; end` structure. It treats lists as a first-class citizen, making operations on groups of files or strings far more intuitive than the string-splitting gymnastics required in Bash. The syntax is more consistent and readable, closer to what you might find in a high-level programming language like Python or Ruby. This means that while you can't just copy-paste most Bash scripts and expect them to run, writing new scripts in fish is often a more logical and less error-prone experience.
Functions Over Everything
In the world of Bash, `.bashrc` or `.bash_profile` files are often a sprawling collection of aliases and exported environment variables. Fish reimagines this system by heavily favoring functions. Almost everything, from your prompt to what you might think of as an alias, is a function. For example, instead of a cryptic `PS1` variable, you customize your prompt by editing the `fish_prompt` function. Creating an alias is still possible, but fish encourages using functions or 'abbreviations'. Abbreviations are a clever feature where a short string you type is expanded into a longer command, making it clear what's actually being executed. Functions can be 'autoloaded,' meaning fish only loads them from their dedicated files when they are first called, which keeps the shell start-up time fast and the configuration organized. This function-centric design provides a powerful and tidy way to extend the shell's capabilities far beyond simple command shortcuts.
Configuration Without the Cryptic Files
The power of fish extends to how it manages its own settings. Forget sourcing multiple profile files. Fish uses a clear directory structure, typically `~/.config/fish/`. But the real power comes from its universal variables. By setting a variable with `set -U`, you create a variable that persists across all shell sessions and even reboots, without ever manually editing a configuration file. This setting is stored on disk and shared among all fish instances. For more complex configuration, fish even offers a web-based interface. Running the `fish_config` command launches a page in your browser where you can visually browse and select themes, view your functions, variables, and history. This makes customization accessible in a way that editing text files never could, perfectly encapsulating the fish philosophy: making powerful features simple to discover and use.
