• slazer2au@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      2
      ·
      2 days ago

      Na, that is you not reading the Frequently Asked Dumb Questions

      Q: What about team collaboration?

      A: It’s a text file. Put it in Git. You know, that thing you should be using anyway? Now your requests have version control, code review, and diffs. For free. Revolutionary, I know.

      Q: But Postman has testing and automation!

      A: So does cURL in a shell script with || and && and actual programming languages. You want assertions? Pipe to grep or write a 3-line Python script. Done.

      • FizzyOrange@programming.dev
        link
        fedilink
        arrow-up
        3
        arrow-down
        2
        ·
        1 day ago

        Lol, I know absolutely nothing about Postman but seriously suggesting Bash scripts, curl and grep as a way to test APIs is a nice way to tell people not to bother listening to your worthless opinions!

        A Python script is far more reasonable.

      • Amju Wolf@pawb.social
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        2 days ago

        Soooo you’re not actually arguing for cURL but for bash scripts and potentially something else.

        And now you come across all the issues that come with that, like portability, the inevitable messiness of Bash (and the fact that people actually need to learn it unlike a GUI tool that uses simple JS for scripting), and you lose all the convenience of a nice UX and stuff like validation that comes with it.

        In other words your argument is about as valid as people who argue that vim is the peak of IDEs and noone ever needs anything else. Which - I really hope - you realize is a bit crazy.

        • slazer2au@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          2 days ago

          What is more crazy.

          1. using tools that are already on your system with zero enshitification potential.
          2. using a wrapper for 1 that has already been enshitified before and who knows when the replacement tool will go through the same thing.
          • Amju Wolf@pawb.social
            link
            fedilink
            arrow-up
            2
            ·
            21 hours ago

            There are even open source tools that do the same thing.

            Also, yeah, if something solves a problem, it can be worth it to pay for it even if it’s proprietary.