My Blog

What! Why Do You Use NixOS?

2026-04-03T00:00:00+00:00

Previous Story
NixOS</a> </h2> While learning programming, I tried a bunch of different languages. Last year I started learning C++, and that pulled me toward systems programming. I like systems I can reason about. I installed NixOS out of curiosity — how does a distro manage to configure an entire system in a single declarative configuration? Can I actually use that? I wasn't even looking to switch from Arch. But the idea felt too interesting to ignore. I was following a video where the guy was setting up Flakes and Home Manager simultaneously, which... is a lot for a first install. But I got through it. Anyways, The configuration, It's almost like a pure function: same config in, same system out. Every time. No hidden state, no "works on my machine" nonsense. That's just... beautiful. And then there's the reproducibility. nix develop gives me isolated, reproducible dev environments without polluting my system. It's like mathematical scoping — variables don't leak. From a FOSS and privacy perspective, NixOS ticks all the boxes too. Fully open, massive community, and you have complete, auditable control over what's on your machine. No black boxes. Also — and this is huge — rollbacks. Every generation of your system is kept. Broke something? One command and you're back. It's like Git, but for your entire OS. This is too noob saying. Though I'm still noob on NixOS. There's so many stuff I need to know. This is too small saying about NixOS. I want to write more about NixOS. Is it a steep learning curve? Absolutely. The Nix language took me a while to wrap my head around — it's a lazy, purely functional language, which is its own kind of rabbit hole. Whatever, I'm not going back. </blockquote> My first basic configuration:</a> </h3> { config, pkgs, ... }: { imports = [ ./hardware-configuration.nix ]; boot.loader.systemd-boot.enable = true; boot.loader.efi.canTouchEfiVariables = true; networking.hostName = "nixos"; networking.networkmanager.enable = true; users.users.rafid = { isNormalUser = true; extraGroups = [ "wheel" ]; shell = pkgs.bash; }; environment.systemPackages = with pkgs; [ git curl wget vim neovim ]; system.stateVersion = "25.11"; }</code></pre> A funny true meme from other site:

Customizing The Bash Shell 2025-11-28T00:00:00+00:00 Before Anything</a> </h3> BASH - Bourne Again Shell Bash used for General-purpose programming and scripting and also a 'Shell' (This mixed here). Most people now just use Zsh or Fish. But I think Bash is actually better than any other shell. Because, its stability and broad compatibility. Also the general command-line use across most Unix systems. Tools mentioned: ble.sh, Starship, fzf ble.sh — replaces Readline with syntax highlighting, autosuggestions, vim/emacs modes, better completion</li> fzf — fuzzy finder that revolutionizes history search, file navigation, git operations</li> Starship — cross-shell prompt that is minimal, fast, git-aware, and highly customizable</li> </ul> Install these first </blockquote> Configure bash first</a> </h3> You can enable Vi/Vim mode in your shell by adding set -o vi</code>. And use the shell like Vim (I mean the keys). First thing you need to do after installing fzf and Starship is setting up paths: add this eval "$(fzf --bash)" eval "$(starship init bash)"</code></pre> You don't have to customize ble.sh and fzf for basic use, for customizing Starship, you can find official presets here</a> You can bind keys for shortcuts, add aliases and create function. Here's is an example: # create function: open_file() { local file file=$(fzf --preview 'bat --style=numbers --color=always {}' --border --select-1 --exit-0) if [[ -n "$file" ]]; then nvim "$file" fi } # Bind key: run the function bind '"\C-f":"open_file\n"' #Alias alias kiss = 'mkdir -p' # since touch used to create new file!</code></pre> Just like that, when you enter Ctrl+f, it runs the function (in this function it will open a selected file with fzf). Some different (and pros)</a> </h3> Bash is good enough for everything, default everywhere, POSIX + useful extras.The main differences show up when scripts grow or need real structure. Bash's error handling is clunky (fighting with $?</code>, set -euo pipefail</code>, and traps), data structures are weak (arrays yes, but proper dicts only since Bash 4+, and no easy sets/objects), and anything beyond integer math or complex JSON parsing forces you into awk/jq/bc hacks that hurt readability fast. # Example set -euo pipefail # strict mode trap 'echo "Error on line $LINENO"' ERR</code></pre> The key pros of Bash shine brightest for fast, lightweight, system-level automation. Shell: While zsh and fish feel snappier out-of-the-box with built-in autosuggestions and nicer syntax, Bash remains king for pure compatibility. Every Linux distro, container , and cloud VM has Bash — no surprises when your script runs on a minimal server. Zsh scripts are mostly portable, but fish syntax breaks POSIX/Bash compatibility hard, so you end up rewriting things anyway. If you're scripting a lot (cron jobs, Dockerfiles), Bash's "write once, run everywhere" wins. Interactive use? That's where ble.sh + fzf + Starship close the gap — you get highlighting/suggestions + fuzzy finding, but stay in Bash. Also, 'Oh My Bash' for plugins. Bash Scripting Guide</a> </h3> Bash Guide</a> :respected community resources with in-depth Bash Guide, FAQ, Pitfalls, and best practices. You can find more documentation on the internet. see this reddit post</a> World, I'm Here Whether You Like It or Not 2025-10-28T00:00:00+00:00 Hello World. (October 28, 2025) </blockquote> Uhmm......</a> </h3> I never post anything on the internet. This my small piece of the web.. (uhm, Welcome) So, I want to share that 'things are not going well (now)', before that I want to say something about myself. I'm interested in Programming (I found it when my friend showed me a simple calculator program on his android phone, Sometimes, I feel lucky I'm trying to program) and I want to stick with it. guess what? I've been on this awesome Programming journey for the past 3 months after I got my second computer. I enjoyed mostly. But after few days, I always having the thought "I'll do it later!", And that's why I'm now frustrated. (I invested quite more time in Vim and Linux). Nothing changes (actually), I just jumped around programming languages (Python, JavaScript, ... ). But the goal was different "Web development", Now I hate it. Not because it is hard or something like that. I just didn't continue, I believe, Programming is not just learning/knowing programming language(s). But my progress is just didn't work out. I'm learning 'Rust' (What?</del>) last few days. This is might be strange. I found Rustlings (Rust errors solve, more like a game) enjoyable. Also, Their documentation is solid. So, I started sucking around Rust. I'm pretty sure I'll pause this (too). I just change my idea/(x) so rapidly. Maybe in 3-4 months in another level (in negative direction!). What I'm Hoping</a> </h3> I do want to get better at coding in the real world, contribute to projects I like. The goal is very simple learn, contribute, and see where it takes me. Why this now?</a> </h3> This is my first blog post you are reading right now and i think, there will be more to come. I'm focusing on core programming. Here to share.. maybe some, programming related blogposts and something weird I want to write. In addition, I want to write about the topics I’m passionate about, like tools, search, recommendations, and situations. {: .prompt-tip } </blockquote> Creating this site</a> </h3> I build this site with Hugo yesterday. Hugo is a static site builder. So, I didn't have to write any html or CSS, just added a Markdown and you see.. edit(feb-26): I recreated this webpage with Jekyll. (you know, changes!) Almost same as Hugo. Conclusion</a> </h3> This post is largely a statement of intent (and a little document), my unstructured thought, it looks creepy but, just had to take the first step of writing my blog. From here on out I plan to focus on 'be more focused and technical' and dive into the Open Source Ocean. At last, I want to say 'Hello World'. That’s all for now.

My first basic configuration:</em>

Some different (and pros)
Bash Scripting Guide</a> </h3>
Bash Guide</a> :respected community resources with in-depth Bash Guide, FAQ, Pitfalls, and best practices. You can find more documentation on the internet. see this reddit post</a></p>

Bash Scripting Guide</a> </h3>
Bash Guide</a> :respected community resources with in-depth Bash Guide, FAQ, Pitfalls, and best practices. You can find more documentation on the internet. see this reddit post</a></p>

Uhmm......What I'm HopingWhy this now?</a> </h3>
Creating this siteConclusion

What I'm HopingWhy this now?</a> </h3>
Creating this siteConclusion

Why this now?</a> </h3>
Creating this siteConclusion

Creating this siteConclusion

Conclusion

My Blog

What! Why Do You Use NixOS?

NixOS
My first basic configuration:</em>

Customizing The Bash Shell

World, I'm Here Whether You Like It or Not