One of the reasons I find Linux to be largely superior over Windows is its use of package managers. For a Windows user, this might seem like a nit-pick when comparing the two operating systems but it really is a game changer. The implementation of package managers varies between different families of Linux distributions, and I'm writing with Arch Linux's package manager pacman
in mind, but the idea and core concept is the same no matter the distro.
I realise I need to make more clickbaity, more digestible blog posts so I will now expand into the territory of Top 5 lists. This is how you do it right?
The Linux terminal is an extremely powerful tool, allowing you to access and control your entire system just by typing commands. In addition, there exists a seemingly infinite amount of command-line utilities. What characterises all of these are just how lightweight they are, while not compromising in its power and flexibility.
When I first tried out Linux, one of the things that stood out to me was its file structure. It is structured in a completely different way to Windows, and I believe that when you understand it you can see how it clearly is a superior way of structuring things.
As I've switched from the dumpster fire that is the Windows operating system, I've begun going about my way of managing my Linux system in a very particular way. These guidelines, or rules, have purely existed as ideas in my mind, and I haven't thought about writing them down until now.
git commit -m "Initial Commit"
The first blog post is always something special. So therefore I chose to put a boring placeholder post as the first one.