My objective is to ditch windows & utilize my triple monitor desktop as a cockpit style dashboard for my homeserver & lan devices along with always open widgets like music, calculator, etc.

There was another post yesterday about this and the community recommended Mint & Pop OS the most. However, I am not looking for windows-like. I want a new & fresh experience like using a smartphone for the first time or switching from ios to android.

Distrochooser.de recommended kubuntu to me.

So I have some questions:

  1. What are the building blocks of a distro? Things that separate distros from each other. Like I know 2 - Desktop Env & Package Managers. Are there others, what are they or where do I find a list? I would like to compare these blocks and make it a shopping experience and then pick the distro that matches my list. Is this approach even valid?

  2. How do I find and compare whats missing from which distro? For eg. if I install mint, what would I be potentially missing out that may be a feature on another distro? How do I go about finding these things?

  3. What are some programs/ widgets/ others that are must haves for you? For eg. some particular task manager

  4. What are the first steps after installing linux? For eg. In Windows, its drivers, then debloat and then install programs like vlc, rar, etc.

  5. I read on some post, a user was saying that they want to avoid installing qt libraries. Why would someone potentially want that? I have never thought of my computer in such terms. I have always installed whatever whenever. The comment stuck with me. Is this something I should be concerned about?

  6. Should I not worry about all of the above and just pick from mint, pop and kubuntu?

  • Display Name@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    10 months ago

    Great point.

    You state that distro maintainers may fix vulnerabilities that app developers don’t fix timely or at all.

    Right now fedora keeps their own flatpak repository, for other reasons but fedora may fix dependencies, runtimes, etc. If they wanted to. Meaning, it is not a flatpak issue in itself.

    Debian maintainers could instead of packaging for debian, package for their own debian-flatpak repository - which actually could be used by any distribution because it’s flatpak.

    I like the idea of having a party inbetween the lines, kind of like fdroid for linux but with security in mind.