• Integrate777@discuss.online
    link
    fedilink
    arrow-up
    28
    ·
    14 hours ago

    NixOS consist of a bunch of options that you define using the nix programming language. Since it’s a programming language, everything is well defined and organised into single place.

    Technically, someone could build a GUI configuration editor with sane defaults and clearly organised pages of settings, which generates a configuration for you. This could immediately change NixOS from the most tedious to a relatively easy to use distro.

    • iopq@lemmy.world
      link
      fedilink
      arrow-up
      20
      ·
      11 hours ago

      They already built a GUI editor, but a programmer made it so it is actually harder to use than the text file

    • AnUnusualRelic@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      10 hours ago

      And windows users are well known for their mastery of esoteric programming languages. Such as… um… ah… batch files, which, well, some of them can write. If they’re not more than four or five lines.
      But that counts, right?

      • Oniononon@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        1
        ·
        17 minutes ago

        Linux users can’t regedit. Regedit uses some weird programming language only known to a few windows grand masters.

        It basically represents values with 16 possible symbols, ranging from 0 to f. We call it sixteendecimal. Very advanced. But nobody knows what they mean yet.

        This should give you linux users a pause the next time you belittle windows users for their lack of computer knowledge!

      • leftzero@lemmynsfw.com
        link
        fedilink
        arrow-up
        1
        ·
        9 hours ago

        Batch files¹, powershell, visual basic if you use Office, Lisp if you used AutoCAD back when macros were written in Lisp… 🤷‍♂️


        ¹- And, frankly, I doubt setting up NixOS is particularly more complex than setting up an autoexec.bat boot menu back when some programs (well, games are programs) wanted extended memory and some others wanted expanded memory (couldn’t have both modes at the same time, of course), and you had to make sure the drivers loaded in the most optimal order (which could vary depending on the aforementioned memory expanders, and which drivers the specific game actually needed) to fit as many as possible of them and DOS in high memory leaving as much as possible of the 640KB of system RAM free for the program… and I’m not even getting into the whole IRQ thing for soundcards and whatnot… and we had to do it all without Internet, learning by trial and error, or word of mouth, or from magazines…