recently i just finished building a new pc. mostly for gaming since my only exposure to linux is steam os and i heard its uses arch with kde plasma so i try to emulate it as close as i can. however soon i realized how different it is and it requires more setup than i initially thought. i spent a whole day or two setting it up and i read now im responsible on maintaining it, what does it mean? is it just finding and testing drivers? or system update? what is the easiest way to do it? and what i getting myself into?

when i was about to install steam i found a tutorial on it with 3 - 4 pages full of text and was a bit overwhelmed, i decided just set it up using discover with flatpak, the problem is when i was about to find out how to do that i read mostly people really hate when you ask how to enable it in arch, is it really bad? should i just use konsole instead?

im not very tech savvy and at first I was really reluctant to use konsole but since i decided to use arch its inevitable that i have to use konsole and so far its not that bad, yet.

I’m just wondering for the long term, should i just change distro? or i should just powertrough arch and see where it goes.

thank you for your time.

  • pyssla@quokk.au
    link
    fedilink
    English
    arrow-up
    3
    ·
    10 hours ago

    Honestly it sounds like you’ve mastered a completely new kind of operating system, based on Linux but evolving in its own direction

    Thanks for the compliment 😅. I do think there’s some truth in it being a new kind of Linux-based OS. But it’s not as big of a departure like say NixOS. Heck, I’d argue it’s grounded within a relatively basic premise: What’s the minimal amount of effort required to make our current Linux systems attain desirable qualities like being reprovisionable and anti-hysteresis? The whole bootc-shebang is just leveraging existing container technologies (I’m sure you’re familiar with Docker) to the Linux you run on your computer.

    and there’s probably only a handful of people using it at that level.

    If we would (perhaps arbitrarily) choose for “that level” to be “crazy enough to create and run their own image”[1], then it’s true that our numbers are probably only in the order of hundreds. Though, the knowledge required to build your own image is (almost) equivalent to the knowledge one ought to have to create their own OCI image; you know, the very same used for Docker, the container technology that represents a billion dollar industry.

    It’s pretty cool to learn more about, so I appreciate what you’ve had to say.

    I appreciate it. I like conversing with you as well 😊!

    I already know and love traditional Linux and don’t see a compelling reason to change

    That’s perfectly valid.

    I don’t think it’s the way to point a newcomer.

    Please allow me to explain why I differ on this:

    The beginner has no preconceived notion on how Linux is ‘supposed’ to work. As such, they will adapt to whatever you throw at it. Be it Mint, Arch or Fedora Atomic. Heck, it’s undeniable that out of these, Fedora Atomic works the closest like their phone. Which has undoubtedly become the most recognizable OS for your average Joe.

    FYI, Fedora Silverblue was my foray into Linux. The first one or two weeks definitely gave me a hard time, but that was over three years ago. If I was able to survive in such a ‘hostile’ environment, then newcomers should have absolutely no trouble getting onboard with the introduction of Bazzite (and the other uBlue images).


    1. As that’s most likely my biggest Fedora Atomic achievement. ↩︎