I’m talking about like your mom if she started using Linux, and just needs it to be able to open a web browser and check Facebook or her email or something. A student that just needs a laptop to do homework and take notes, or someone that just wants to play games on Steam and chat on discord.
I’m working on a Windows - > Linux guide targeting people like this and I want to make sure it can be understood by just about anybody. A problem that I’ve noticed is that most guides trying to do something like this seem to operate under the assumption that the viewer already knows what Linux is and has already made up their mind about switching, or that they’re already pretty computer savvy. This guide won’t be that, I’m writing a guide and keeping my parents in mind the whole time.
Because of this there’s some things I probably won’t talk about. Do these people really need to know that it’s actually GNU+Linux? No, I don’t think so. Should I explain how to install, use and configure hyprland, or compile a custom gaming kernel? I dont think that’s really necessary. You get what I’m saying? I don’t want to over complicate this and scare people off.
That being said I also want to make sure that I’m not over simplifying by skipping on key things they should know. So what are some key concepts or things that you think even the most basic of Linux users should understand? Bonus points if you can provide a solid entry level explanation of it too.
Trusted sources, only.
Same as Windows, Android: sideloading (tarballs, flatpaks, snaps whatever) is a no-no.
Like
bash curl install.shbadI’m not sure this is great advice. In principle it is. But you can’t tell a windows user “yes. You know how many of the programs you used to use are not available because they don’t make a Linux version? Well a lot of the ones that do you shouldn’t use even though the distro supports it for reasons you don’t understand”
That is better advice for an intermediate used learning about the dangers (or lack there of) sideloading.
In general o disagree with your stance on a basically semantic reasons: the definition of a trusted source. If I trust a software manufacturer and they tell me to use their flatpak, it’s fine because they are trusted, regardless of the format. What I do not like are things like the AUR