• andrew@lemmy.stuart.fun
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 year ago

      To play the opposite team a bit here, I like the idea Android uses of Intents for something like this. I think it falls apart a bit in reality because app companies kinda want you in their garden and so don’t often do the work to keep things interoperable. That and the use cases from users on phones don’t frequently involve cross app functionality. But the ability is powerful for apps to say “my app needs a user photo” or one of my faves “my app needs a pgp provider (for the password store app)” and then let the other app do that piece of functionality as determined by the OS, which tracks a lot of those providers and lets the user decide which to use.

    • grue@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      1 year ago

      https://en.wikipedia.org/wiki/Automator_(macOS), or in general, https://en.wikipedia.org/wiki/Visual_programming_language

      'Course, there’s a reason those things basically never catch on, which is that they don’t actually reduce the inherent difficulty of figuring out the algorithm, and for anything non-trivial messing with a whole bunch of drop-down lists and shit is more cumbersome than just typing the damn thing.

    • Limeey@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      This right here, you can gui a single program, but with pipes we can chain nearly infinite programs. No way can you make a gui that is that flexible, I refuse to believe until I see it

    • Dmian@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      3
      ·
      edit-2
      1 year ago

      Are you talking about sending the output of one process to the input of another?

      I think the shaders I’ve mentioned are a great example of that: you do something in a block, then send the result to the input of another block.

      Sorry if it’s not what you mean, but my point is that, with some effort, you can create a visual representation of even the most abstract concepts. Physicists do this constantly. If we can make a visual representations of 4D, for example, what prevents us from doing the same for programming logic? Or for commands?

      • Avid Amoeba@lemmy.ca
        link
        fedilink
        arrow-up
        7
        ·
        1 year ago

        Yeah, and doing this would take significantly longer to use every time than typing up a chain of commands in a terminal.

        • Dmian@lemmy.world
          link
          fedilink
          arrow-up
          4
          arrow-down
          4
          ·
          1 year ago

          Agreed. But that’s not my point. My point is that it can be done.

          And in some cases, even if it’s less than ideal, and is way more cumbersome than using a CLI, you are helping non-tech-savvy people do things they couldn’t do any other way.

          • Kecessa@sh.itjust.works
            link
            fedilink
            arrow-up
            5
            arrow-down
            1
            ·
            1 year ago

            Linux users: Non tech savvy people? Yuck

            Also Linux users: Everyone should be running Linux instead of Windows!

            • grue@lemmy.world
              link
              fedilink
              English
              arrow-up
              7
              ·
              1 year ago

              Put those two statements together and the logical conclusion is that Linux users simply want everybody to be tech-savvy (although I’d use a different term: computer-literate). What’s wrong with that?

              • Kecessa@sh.itjust.works
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                Not everyone has the same interests. All car people would love everyone to be car people. All bikers would like everyone to ride bikes. The difference is that you pretty much need to be interested in computers to run Linux.

                • grue@lemmy.world
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  1 year ago

                  It’s not about having the same interests; it’s about the fact that the single distinguishing factor between a computer and any other mere machine is its ability to be programmed, and you therefore don’t really know how to use a computer unless you can create novel workflows to solve your own novel problems. If you can’t script, you aren’t literate in the 21st century.

                  All car people would love everyone to be car people. All bikers would like everyone to ride bikes.

                  It’s funny you should use those particular examples, (and not just because they also happen to be things I’m particularly passionate about).

                  In particular:

                  1. If you live somewhere that’s built wrong (i.e. is car-dependent) and you can’t drive, you’re homebound. It’s not about being a “car person;” it’s about the skill being necessary to function.

                  2. Conversely, places that aren’t built wrong are precisely those that facilitate cycling as a matter of design and policy. It’s not about what “bikers would like;” it’s about what empirically works best for a functioning city.

                  • Kecessa@sh.itjust.works
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    edit-2
                    1 year ago

                    I used to examples because in both cases it’s things you can do without it being an interest to you, you do it out of convenience, no need for a deep analysis, I could have said people who love camping would like everyone to love camping, it would be the same thing.

                    And just like those things, people use computers out of convenience and it’s perfectly acceptable that some people don’t have a deep interest in them and therefore wouldn’t be interested by an OS that requires a deeper understanding of computers to make it work.

          • grue@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            Nobody capable of defining an algorithm in a visual flowchart like that isn’t also capable of doing it in a CLI (or at least, in text in general – writing a script). It’s thinking through what you want to happen that’s the hard part; expressing it in the UI is trivial in comparison.

            • Dmian@lemmy.world
              link
              fedilink
              arrow-up
              2
              arrow-down
              3
              ·
              edit-2
              1 year ago

              Some people have problems remembering commands, for example. And it’s easier for them if they can see it.

              Yes, you can teach a kid to program (with some effort), but there’s a reason why Scratch presents logic units with shapes and colors and a GUI.

              There are many reasons why a visual representation may be easier to grasp than just resorting to memory and remembering abstract concepts.

              I mean, do you remember everything that you write? You’ve never had to visit Stack Overflow to remember how to do something, because you forgot the exact syntax of an operation? Now, how about if I put things visually in front of you? What would be easier?

              • howrar@lemmy.ca
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                I’ve probably spent more time looking up how to access specific functions in a GUI than for CLI.

        • Buddahriffic@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Things like that have been around for a long time. It was like two decades ago that I saw this shader scheme in softimage|xsi.

          For implementing something like that, each node in that graph would have an array of inputs and outputs. Each of those would have a type like vector, scalar, colour, string. Then you only allow connections if the inputs and outputs match types (though you can also have conversion nodes or selectors that say pick the red channel of a colour to turn it into a scalar). Each input can be set to a constant value instead of connecting something else to it. Outputs don’t need to be connected, which is mostly useful if a node has multiple outputs. Then each node has an evaluation function that takes all input parameters and maybe internal configuration parameters (though you might as well make everything an input param since there’s no real functional difference) and uses them to calculate the outputs, which it then sends on to anything connected to those.

          I’m not much of a UI guy but displaying it for the GUI would just involve drawing boxes or some shape for the node, then spaces for each of the inputs on the left side and outputs on the right side maybe colour code them by type, and lines running along the connections. Then just add the name and/or other visual information you want to display and positional information to let users move it around their work area.