this post was submitted on 05 Jan 2024
17 points (100.0% liked)

Linux

8332 readers
239 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
 

Hiya,

I don't suppose anyone has a good source / 15 minutes and a drive to lecture a Linux noobie on some basic Linux functions or things to read up on?

Perhaps unsurprising given the gestures wildly to everything, but I have been planning to switch over to Linux on my home machine for a long time now and I feel like Microsoft slowly, inexorably, forcing the swap to Win11 is as great an excuse to finally bite the bullet as I'm likely to get.

A bit of background, I am an IT guy with many years of experience in Windows and some small bit in Mac. I am an experienced coder with a good fundamental understanding of Unix environments and how to make systems talk to each other. Im comfortable with deep, technical stuff, but, especially in new systems I have a bit of a hard time with abbreviations and acronyms. So I don't need a whole "Linux for Dummies" as I feel like I have a pretty firm grasp on the basics. I just want to know if there's any convenient tips or tricks to make the transition easier.

For example, I have literally no idea what distro I should use lol. I've spent a while researching but given how customizable it all is, after a while it all kinda just mushed itself into a gray maisma in my brain. I use my home machine almost exclusively for gaming and some light coding projects, but I also want to be able to play around with it and do some independent learning.

I just need a good source that can give me the basics on where and how to translate my knowledge of Windows to insert Linux distro. I know it's a completely new OS so I will need to learn a lot of new things. But at their core computers are computers so some things need to be the same, I'm just not sure what to look for.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Rossphorus@lemmy.world 5 points 11 months ago (1 children)

People have made distro recomendations already, so I want to talk a bit about what makes a distro a distro: application repositories and management, update cadence, and what's installed by default. That's pretty much it. Anything else can likely be transplanted from distro to distro.

Out of the default applications by far the most important is the desktop environment. Have a look at Gnome, KDE (and others, cinnamon, etc.). Pick something you like the look of. Gnome is known to be closer to Mac styling and sentiments, including the our-way-or-the-highway philosophy, limited customisability in the name of consistency, etc.. KDE is the 'we heard you like customisation so we put customisations on your customisations' kind of environment.

Update cadence really boils down to one of two things - do you want a new OS version every few months where the distro maintainers manually release a bunch of software all tested together (e.g. Debian, Ubuntu, Fedora), or do you want each application released individually after it's been tested to work with everything else (Arch)? Note that the former are sometimes called 'stable' releases but not because they are less likely to crash, but because there are simply fewer updates. The latter are called 'rolling' releases.

The application management philosophies are a lot harder to nail down, especially as a newbie. You will probably just have to accept that the first distro you try will likely not be the one you settle on. For instance I started with Ubuntu until I got fed up how difficult it was to install anything not found in the main repository (a surprising amount of software): In Debian-based distros (like Ubuntu) unofficial software is fragmented across thousands of 'personal' repositories that you must manually add URLs and signing keys for, it feels very clunky. Because they are personal respositories it's easy for the owner to abandon it or just not push updates and you won't even notice until it breaks after a system update. Once I had some Linux experience under my belt I found the Arch repository style much easier to work with: One central official repository, and one 'unofficial' repository. I've heard Fedora has a similar system.

But the single most important piece of advice - just pick something. The great thing about Linux is it makes hopping distros easy: A package manager makes it trivial to export a list of installed programs so you can reinstall them on your next distro. You won't be enslaved to a distro once you decide, so just pick something and use it for a bit. Learn what you like and what you don't. Use that to decide on your next pick.

This is a pretty good starting point, but I would like to add that Flatpaks and Flathub can make software stupid easy as well. There are a few distros that have support right out of the gate.