• AnimalsDream@slrpnk.net
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 hours ago

    I like both, but I think I would like cli better if the syntax were more expressive, and more akin to natural human language.

    • jj4211@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      5 hours ago

      I can appreciate the desire for “you know what I meant” CLI interaction, but shudder at the verbosity of natural language in a lot of these cases.

      • AnimalsDream@slrpnk.net
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 hours ago

        I think there has to be a happy medium, but I guess it depends on personal preference. It’s not like brevity can’t be achieved through things like aliases anyway. I just want text-based computer stuff to look a little more like something Inform 7.

    • GaumBeist@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      5 hours ago

      The hardware of a computer is not designed to handle natural language parsing. Techbros with just enough knowledge to be dangerous will say it’s a matter of complex-enough software, but it’s more that human brains are not Von Neumann machines

      • AnimalsDream@slrpnk.net
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 hours ago

        Friend, I have studied my fair share of programming, I get it. I’m not saying there should be any significant difference to the way information is processed, or what kind of processing occurs. Just that the syntax itself trades off a little of it’s brevity for a little more readability, like something along the lines of the Inform 7 but still within the boundaries of how the programs and cli normally operate under the hood.

        • GaumBeist@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          3 hours ago

          Oh, for sure. All it takes is me looking at an Awk one-liner to make my headspin. Give me a simple “for each line in $FILE, reformat MM/dd/yyyy as dd/MM/yyyy” instead of… whatever that looks like in Awk.