archstrap VS sysfetch

Bootstraps Arch Linux from existing Linux systems — https://github.com/wick3dr0se/archstrap

My first GitHub commit ever and first time writing a BASH script – Nov 19, 2021: https://github.com/wick3dr0se/sysfetch/commit/4190caeb6fb1f14eedffc9ec34b4dc0cf637b160

A system information fetch utility I wrote as my first project, somehow most popular of anything I've wrote — https://github.com/wick3dr0se/sysfetch

Web development lead me to Linux where I got into scripting. It wasn't a week into learning BASH that I started making sysfetch. I've made many more useful utilities for Linux (mostly for personal use). Most recently(last week) I started making a BASH framework to extend BASH and make it easier to use. I ran into several things BASH can't do pretty quickly. Now I am learning C and working on an expression evaluation algorithim. I plan to pull C into my BASH framework, making much more possible.

I do btw!! I wrote a Neofetch alternativethat prints btw versioning on Arch systems too lol

I don't document many projects because they are for my usage. prompt.sh is well documented as well as bashin and of course sysfetch. Also Mac isn't suck on BASHv3 it can be updated. I hear that a lot but I've already had contributors prove that wrong. If you look at sysfetch it was all external commands on commit 1. Also external commands such as awk, sed, grep have absolutely nothing to do with BASH. Those are command usable from and script language. BASH has beautiful bashisms that can do a ton of things. Sysfetch was not usable from WSL, Mac or BSD before the usage of builtins. At one point it was usable from all 3 but I only care about Linux. Contributors can handle other operating systems again if they desire. I never plan to support proprietary bits anyway. It works on BSD already. Another thing to note is many operating systems have different flags for external commands like awk or sed and as a result do different things

I have wrote some utilities for Linux such as sysfetch(which is packaged in the AUR). A good starter project I wrote is a simple type test(23 SLOC) I recently did. So, as you can see, the possibilities are pretty limitless

The pipes themselves aren't slow. It's that you're piping multiple external commands together. If you build a script that calls those commands several times you will see the difference. Challenge yourself to build things with builtins and then use the time command when running the script to see the difference. I knocked off over 600ms of execution time from sysfetch

There is several other useful scripts in that repository. I apologize for not having documentation. I do have a neofetch-like alternative called sysfetch, and a BASH framework I recently started. I ran into some things I couldn't achieve in BASH. So I'm going to work on a BASH framework in C next.