Forem: Sakib Reza

Bash vs. Zsh vs. Fish: Which One Should You Actually Use?

Sakib Reza — Thu, 16 Apr 2026 11:09:24 +0000

Let’s be real for a second.

If you’ve ever opened a terminal and thought, “Wait, am I using the right shell?” — you’re not alone. For years, I just used whatever was there. Usually Bash. Sometimes Zsh if I was on a friend’s Mac. But then I heard people raving about Fish and suddenly I felt like I’d been living under a rock.

So I tried all three. Here’s the honest, human take.

Bash: The Old Reliable

Bash is like that pair of jeans you’ve had forever. Not stylish, not exciting, but they fit and they work.

It’s everywhere. Seriously. Every Linux server, every Raspberry Pi, every Docker container — Bash is there. If you write a script in Bash, you can be 99% sure it’ll run on anything without installing extra stuff.

But here’s the thing: using Bash interactively in 2025 feels… dated. No syntax highlighting. No autosuggestions. Tab completion is basic. You can add plugins and tweak your .bashrc until your fingers hurt, but out of the box? It’s a bit rough.

Verdict: Great for scripts, boring for daily typing.

Zsh: The Power User’s Sweet Spot

Zsh is what happens when Bash goes to the gym and gets a cool haircut.

It’s still compatible with most Bash stuff (which is huge), but it adds a ton of quality-of-life improvements. Better tab completion. Globbing that doesn’t make your brain hurt. And then there’s Oh My Zsh — a community-driven plugin system that turns Zsh into a beast.

Want a cool prompt with Git info? Done.
Want to type docker and hit tab to see all your containers? Yep.
Want aliases for everything? Go wild.

The only downside? You can go overboard. My Zsh config once took 2 seconds to load because I had 47 plugins. That was on me, not Zsh.

Verdict: The best all-rounder. Most developers will love it.

Fish: The “Wait, That Just Works?” Shell

Fish is different. And I mean different.

You install it, open it, and — oh wow. Syntax highlighting immediately. Autosuggestions in gray that you can accept with Ctrl+F. Tab completion that actually understands what you’re trying to do. It feels like someone actually designed a shell for humans.

Configuration is hilarious: just type fish_config and a web page opens where you can click buttons to change colors. No joke.

But — and this is a big but — Fish is not Bash-compatible. If you copy-paste a Bash script into Fish, it might just laugh at you. So if you live in a world of other people’s shell scripts, that can sting.

Verdict: Pure joy for interactive use. Frustrating if you need strict compatibility.

So Which One Is The Best?

Honestly? There’s no single answer. But here’s what I’d tell a friend:

· Stuck on servers or writing portable scripts? Stick with Bash. It’s not sexy, but it’s safe.
· Want power + compatibility + cool themes? Get Zsh. Install Oh My Zsh. Don’t go crazy on plugins.
· Hate configuring things and just want a shell that feels good? Try Fish. You’ll smile the first time you use it.

Me? I use Zsh on my personal laptop (with about 10 plugins, not 47) and Bash on servers. And I secretly install Fish on new machines just to play with it for a day before switching back.

Don’t let anyone tell you there’s a “right” answer. Try each for a week. See what makes you happy.

Because at the end of the day, the best shell is the one you don’t have to fight.

What shell are you using right now? Reply and tell me I’m wrong — I probably deserve it. 😄

Library vs Framework: Understanding the Key Differences in Programming

Sakib Reza — Sun, 06 Apr 2025 16:13:31 +0000

When learning programming, you’ll often hear the terms library and framework. Both encompass reusable code but in differing contexts. Understanding the distinction between the two helps you choose the most effective tool for your project.

Step-by-step comparison

1. What is a Library?

A library is a group of pre-existing functions or modules from which your code can call in order to get some task done.

Important Features:

You control the flow - Your app calls the library when needed.
Specialized purpose - Libraries do a specific job (for instance, mathematics operations, HTTP requests).
Lightweight - Use no more than what you require.

Example:

React (Library) → For developing UI components. You get to decide how your app should be structured.
Lodash (Library) → Provides array utility methods, object utility methods, etc.

2. What is a Framework

A template is a preformatted arrangement through which your application learns how it should be made. It provides a pre-set structure with pre-formulated rules.

Key Features:

It controls the flow – Your code is placed in the framework's structure.
Complete architecture - Frameworks contain routing tools, database access, etc.
Convention over configuration – You use its conventions for improved scalability.

Example:

Angular (Framework) → Provides a full-fledged MVC web app framework.
Django (Framework) → Handles back-end logic, database, as well as templating.

Key Differences Between Library and Framework

Feature	Library	Framework
Control Flow	Your code calls the library	Framework calls your code (Inversion of Control)
Flexibility	More flexible, plug-and-play	Less flexible, follows strict rules
Size	Smaller, modular	Larger, provides full infrastructure
Usage	Used for specific tasks	Used to build entire applications
Examples	React, jQuery, Axios	Angular, Django, Ruby on Rails

Why Use a Library vs a Framework?

Use a Library When:

✔ You need only specific functionalities (e.g., DOM manipulation with jQuery).
✔ You want more control over your application structure.
✔ Your project is small or requires lightweight solutions.

Use a Framework When:

✔ You’re building a large-scale application (e.g., enterprise software).
✔ You need built-in tools for security, routing, and databases.
✔ You prefer standardized best practices.

Conclusion

Library → A toolbox with specific tools you use when needed.
Framework → A blueprint that defines how your entire house (app) should be built.

The choice between the two depends on your project's needs. Libraries are adaptable, while frameworks promise structure, together with efficiency.

Must-Have GNOME Extensions for a Faster, Prettier Desktop

Sakib Reza — Tue, 25 Mar 2025 22:17:07 +0000

If you're using GNOME as your desktop environment, you know that extensions can greatly enhance your workflow and customization. Here are some of my favorite GNOME extensions that I find useful for productivity and aesthetics.

🚀 Essential Extensions

Blur My Shell

This extension adds a beautiful blur effect to the top bar, overview, and other UI elements, making the desktop look more modern and polished.

Clipboard Indicator

A must-have for productivity! It keeps a history of your clipboard entries, allowing you to quickly access previously copied text or files.

Dash to Dock

Transforms the default GNOME dash into a fully customizable dock. You can adjust its position, transparency, and behavior to suit your workflow.

🎨 UI & Customization

Rounded Corners

Gives your windows and menus smooth rounded corners for a softer, more modern look.

Coverflow Alt-Tab

Replaces the default Alt-Tab switcher with a stylish coverflow effect, making it easier to navigate between open apps.

Top Bar Organizer (Optional)

Helps you rearrange and group system icons in the top bar for a cleaner layout.

⚡ Productivity Boosters

App Indicator

Brings back system tray icons for apps that require them (like Discord, Steam, etc.).

Places Status Indicator

Quick access to frequently used folders directly from the top bar.

Simple Timer

A lightweight timer extension for setting quick reminders or productivity sessions.

Vitals

Displays system stats (CPU, RAM, temperature, etc.) in the top bar—great for monitoring performance.

🎉 Fun & Optional Extensions

Wiggle

Makes windows wiggle when you drag them—just for fun!

Emoji Copy

Quickly copy emojis from a pop-up menu.

Caffeine

Prevents your system from going to sleep when you’re watching videos or giving a presentation.

These extensions help me get the most out of GNOME while keeping my desktop functional and visually appealing. What are your favorite GNOME extensions? Let me know in the comments!

🔗 Find these extensions at: GNOME Extensions

(Note: Some extensions may depend on your GNOME version. Always check compatibility before installing.)

My Development Journey: From Novice to Developer

Sakib Reza — Sat, 05 Oct 2024 16:09:59 +0000

My Journey into Web and App Development 🚀

No developer has the same path; there are always challenges to be faced, things to be learned, and triumphs attained. From a place of curiosity about how websites and applications work, I grew a strong interest in creation and problem-solving. In this post, I shortly share my development story: my journey, the challenges I faced, and what I learned along the way.

Finding Out My Interest 💡

It actually started with a college project: to build a website. That fascinated me so much. The way it feels when something interactive comes right from scratch is just magic. Spending hours experimenting with HTML and CSS was my introduction to the world of programming. My fascination made me understand how different pieces fit together to make an operating website. This marked the beginning of my journey in programming.

Taking My First Step 🎓

Curiosity got the better of me, and to turn this curiosity into something real, I joined a beginner's programming course. I opted for the Complete Web Development course from Programming Hero. It gave me a base for my skills, but that did not come easy. The learning curve was steep, and nights turned into late nights trying to get my code to work.
However, finally getting my projects to come to life keeps me running through frustrating debugging and countless tutorials.

Overcoming Challenges 💪

What was difficult was to keep up the motivation of facing the challenges. Many times in my head, it just felt like there was so much more for me to learn. One thing I did know, though, was that a big problem needed to be broken into smaller pieces-first of all, simpler tasks; secondly, instead of trying to do all of them at once, just doing one allowed me to celebrate small victories.
Joining online developer communities and attending local meetups also played a huge role in staying inspired. Surrounding myself with like-minded people reminded me that we’re all learning at our own pace.

Expanding My Skill Set 🌱

Once I was comfortable with the basics, I soon started exploring the other areas. I dived head-first into web and app development, starting with the languages and their respective frameworks: JavaScript, React, and Node.js. This had opened up the world of dynamic Web apps for me. I didn't stop there; I went ahead to explore Python and its respective frameworks, and databases and even fiddled around with C and C++.
The broad skill set provided the capability of taking up a wide array of projects and working on creating an end-to-end solution.

Stepping into Real-World Projects 🛠️

It has been quite a rollercoaster-uplifting and intimidating-starting to work on actual projects right from learning. Actually, freelance gigs and internships were drilled into practice whereby I learned how to juggle clients' needs, manage time correctly, and solve problems under pressure. Each project was another chance to hone my skills, pushing me toward becoming a better all-around developer. Curious to see what I’ve built? Click here to check out some of my web and app projects!

Continuous Learning 🎯

In tech, if you're not moving forward, then you're only going backward. I use my time to continually learn new languages, frameworks, and tools. To me, learning is one big unending process, whether through online courses, reading blogs, or contributing to open-source projects. This kind of thinking keeps me nimble, and able to adapt to an industry that never stops moving.

Looking Ahead 🔮

I am grateful as I trace back my journey for each challenge, night spent debugging, and all those opportunities that have pushed me to grow. Moving forward, I'm excited about the possibilities. There's so much more to learn and build, and I'm ready to take on whatever comes next!

Conclusion 🎉

The journey of becoming a developer is rarely smooth, but it’s incredibly rewarding. I hope sharing my story inspires fellow developers, especially those just starting out, to push through the tough times and find joy in the process. After all, every step forward—no matter how small—brings you closer to mastery and innovation.