Skip to main content

What's your best Linux OS?

 One of the most controversial questions you could ask a Linux enthusiast is what is his/her favourite Linux OS is?

This is just like that question you know, you know the one.
What came first the chicken or the egg?

Everyone has their reasons and proof to show why their Linux OS is better than yours. But the truth is there is no such thing as the best Linux OS out there.
You see I am not a person to settle this issue once and for all. But in my experience, it solely depends on what you want to achieve with the OS in hand.
I have used OpenSUSE, Ubuntu and its many variants, Linux Mint, Manjaro, Fedora, Pop OS, Elementary OS, Zorin etc. Till now I have never met my "Soul OS". Now I know if you are a Linux user, you are going to use you never used Arch btw. I know, I tried that's as well, but when compared to other distro's Arch won't be the same for me for you, that's the beauty of Arch. And that may bring a new set of controversies to the table as well.
In my defence, I never got to the only distro till now, I have used OpenSUSE but stuck with wifi driver problems that took more than a day from my life during my journey to be a monomaniac on the same topic. I switched to Ubuntu but it was not fun, everything worked as it should be, and I didn't like that part of my journey. Manjaro was a niche OS, and I had issues while upgrading various packages which I installed. Zorin and Elementary were used on my office hardware, and Arch oh I don't want to talk about it...

All I am saying is that of every Linux OS that you could see out there one of them is your daily driver or you could just try each one of them and find your "Soul mate" (but it could take ever and you won't find a perfect partner).
Distrowatch.com is a nice place to start and you will be surprised about the number of Linux OS over there.
Happy Linuxing...

Comments

Popular posts from this blog

A smoooooth operation....

 Backward compatibility...   A word that I used to hear when I started my career. You design your APIs with backward compatibility in mind, don't break anything when you are upgrading, think about this, think about that etc. Well, those teachings from my previous mentors didn't go in vain, as I made a fundamental change in how we report problems @  Gelato .    You see recently @  Gelato , the CS (Customer Support) team moved from A ticketing management system to B ticketing management system, which is a monumental task for all the people involved in the CS team. Even though the fundamental concept remains the same the places, the attributes the concepts, and the naming of different attributes all change if you have this transition. And thus it was a big change for the whole company.    After the decision was taken, the first step was to create a well-written transition document, which the good folks at the CS team tackled. Special thanks to  ...

AI. Will it replace us or...?

AI!! The buzzword is too hot in the market nowadays. Do you have a technical product or an idea? If it doesn't have AI in it, then chances are it's not going to be sold like hot cakes. That is how things have changed lately. It is no wonder why me and my colleagues at Gelato want to see what AI can do in a niche department like customer support and service. And that is exactly what we did. For a company like Gelato, which is in the market for production-on-demand, there are a lot of customer questions you need to answer. It can be related to products, queries about shipping and pricing, and so on and so forth. Thus, our customer support team is always happy to help with these recurring questions. Let's take one example. A customer asked us, "Do you ship to Norway?" Now that is an easy question to answer if you have the knowledge written somewhere where you could refer to it and say, "Yes! As a matter of fact, we do." Following the same thread, the next q...

The alter egos of firebase

 So I was tinkering around the internet as usual, when I came to know about open source alternatives to some of the common tools that we use day in day out. That's when I came to know about firebase alternatives. A service that I used more often to come with a small POC of anything that I want to try out. A couple of the alternatives were  Appwrite  and  Supabase .   I started with appwrite initially, their self-host policy was really awesome and how easy to set it up and get started.    I created a small application on top of appwrite, that I am currently using for my company internal documentation storage. Since it's on top of docker image and resource-heavy I could not deploy it to my AWS free tier server. So sorry about not showing you guys a demo.   After working on top of it, these are my main findings;   Positive   Easy to use, no doubt on that Pretty straightforward documentation on about implementing the features support for a v...