Linux

• repeat the “Don’t sweat it.”
• Ubuntu is a perfectly fine starting point (the other “beginner distro” that’s commonly recommended is LinuxMint)
• »AFTER« you become comfortable with what you have:
  • try familiarizing yourself with the command line
    • far more competent than Windows cmd.exe or PowerShell
    • [email protected]
  • get overwhelmed with all the distro choices available
    • get bitten by the distro-hopping bug (“Gotta try them all!”)
      • and then try Distrobox (“ALL the distros at once!”)
• »THEN« take a look at immutable distros
  • “immutable distro” is a catch-all term that embraces several concepts
    • immutable – the root filesystem is set to read-only – makes it harder to mess up your system
    • declarative – your hardware and packages and configs are declared in a master configuration file
    • atomic / transactional – updates are checked as they’re applied, if it fails, it gets rolled back to a previous “safe state”
    • container / sandbox – ex. Flatpak or Docker or OCI – apps are isolated in their own sandbox and not allowed to mess up anything else

Don't sweat it. There were people doing advanced things in Windows that would probably have blown your mind as well. It's just that most people that use Linux just enjoy tinkering for the sake of tinkering so it's more visible, and Linux lends itself to people doing weird and wonderful things never envisioned by it's creators.

You just started on the road, where you stop is entirely up to you. Just know that the view is way more interesting going this route. Take a few pictures on the way.

Welcome to the Linux community. :)

You will probably never understand everything about Linux and all of its included and associated systems. That's completely fine, no one does! That's why we are many, and it's what asking for advice or help is for. You can just learn whatever interests you at your own pace, and know that there will always be interesting things you haven't seen yet.

It's fine you don't have to understand any of these just use the computer normally and you're good

Think about it this way: going onto Linux communities and listening to what people say can be like listening to car mechanics chat.

But do you need to know what all of that stuff means to drive your car? Nah. But that info could come in handy, if you wanted to modify your car or something like that.

You don't need to know what Wayland/X11, PipeWire, GTK4/Qt6, or anything like that is, in much the same way you don't need to know what PowerShell, Event Viewer, NT kernel, or registry are to use Windows.

You probably think of yourself as pretty knowledgeable regarding Windows, but have you ever studied for a Microsoft certification exam? This in depth knowledge is not something the average user needs for his daily usage, but can be interesting to read/know.

I don't think that this one is as reproducible and declarative as NixOS or Guix.

Oh yep, they are declarative, and that's what we've tried to implement with /system.yaml. pacman hooks and grub configs can be defined through /system.yaml (through a combination of the packages and commands arrays), but Plasma config is per-user and so wouldn't be possible to declare unfortunately :( you can declare GNOME config though, fwiw

(disclaimer: blendOS dev here)

Oh, the main utilities exclusive to blendOS have been documented here: https://blendos.co/reference/ And all the installation/post-install guides: https://blendos.co/install/

For support, we primarily use Discord, although there are plans to set up Discourse eventually: https://discord.gg/fvMpV8ZNxD

(disclosure: blendOS dev here)

It's new to me, I think it's saying that your system is built up by you declaring what you want in a file, a single source that everything comes from.

It's atomic because each action the system takes is carefully completed rather than bailing out and requiring you to fix something.

It's immutable meaning you declare how you want things to be set up and then critical changes stem from those declarations and nothing else. You would obviously generate preferences, save data, etc. but the files that make the system / packages work are carefully locked.

It's like the concept of flatpaks + structured system defining + modern common sense OS operations?

I am no expert, please correct me if I’m wrong

From what I understand, it’s like Nix but Arch based. The /system.yaml file contains all of the packages installed on the system.