Toward the Unknown, Arch and I.

Finally Made the Jump to Arch

I finally made the jump to Arch. It was rushed, I have to say, considering that just two weeks ago I had installed Mint (because Ubuntu was having issues) and after that time I realized I was doing the same thing I did on Mac: trying to emulate everything I already knew, but on a different operating system. And that wasn't what I wanted. I wanted to learn something new, use the terminal, not depend so much on graphical interfaces to get around.

It's similar to what happened to me when I made the jump to Neovim: I wanted something completely different, something that wouldn't make me depend on a file browser or anything so visual. One could ask why, if everything is already solved, to go back and learn something from scratch trying to optimize something that perhaps didn't even need it (I'll talk about that in another post). For now, I managed to install Arch after Wi-Fi gave me more than one headache, and install Hyprland and Waybar.

So Much to Do, Too Much...

I don't know why I keep ignoring the abstraction of programs and operating systems to look for something more low-level. Maybe it's a mental issue, or maybe I just want to try different things. Who knows. For now things look good: it's just a matter of configuring the audio drivers, Bluetooth, the keyboard (a Corne) and whatever else there is left to discover.

This time I'm going to try to do things differently. Let the process be like the one with Neovim: use the terminal more, navigate with it, move and delete files without depending on a folder interface. That's what Arch is for, otherwise I would have stuck with Mac.

More than fun, I hope it's all chaotic. Installing things that don't work, breaking the system, reinstalling everything. That's part of the process, and in part that's why I'm here, on the verge of venturing into the unknown.