arch-linux-installation-guide VS sysfetch

I'm so addicted to it that I wrote an installation guide just to show off to my 'friends'. Even after months of not reinstalling, I can guarantee that I can install Arch from memory in less than 5 minutes. Arch is love, Arch is life

That's exciting! If you need any help installing, I did make an easier to understand guide, good for learning. Althought I recommend ArchInstall these days. I'm glad it can be the first experiment! I have a lot of work to do to get this thing stable. Depending on your DE/WM and other conditions, the script may throw errors so just be weary of that and don't think your system is messed up. It's just that I had no PC for 5 months and I've been back at coding for only a few days now. I rewrote the entire script and dropped probably 100 lines. Seems like I am understanding the logic behind it a lot more now and I should have a functional release this week https://github.com/wick3dr0se/Arch-Linux-Installation-Guide

You should definitely try Arch Linux! The documentation on the ArchWiki is amazing and the community is helpful. I wrote a guide on installing Arch Linux on 86_64 architecture devices and I also have a public repository on GitHub with a stripped version of my desktop with a script to automate the desktop enviornment setup. My setup uses i3wm, feh for wallpaper, thunar, xfce4 terminal, vim as IDE, very basic stuff. I made the guide, script just to make installation easier for myself, since reading the ArchWiki can be cumbersome to say the least

Check out my Arch install guide I recently made for self refrence and to assist a friend. I have instructions on there for GRUB/systemd-boot as boot loaders and NetworkManager/systemd-networkd for networking tools. I use systemd everything because it works very well and I've never had a single issue. Using GRUB in the past I had trouble removing it from multiboot setups and I'd have so much bloat from different themes and versions of GRUB. I prefer to install my boot loader directly in to my EFI system partition, mounted at /boot and then I can manage all my boot files and entries there. You should definitely check it out! systemd-boot auto detects Windows in the EFI partition. I would suggest using NetworkManager for a simple use case, it's configureless and setup just by enabling the service daemon

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

If you'd like a refrence, you should checkout my fetch on first commit and see where it's at now. It's gradually become more performant and full of hardware/software information. I don't work on it much anymore but I'll rewrite it once I get bored of other projects. 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

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.