5 ms·

Postman story: Layoff happened, and we didn't yet have our postman software in our list of services to remove employees from. This is not Postman's fault. One

Postman story: Layoff happened, and we didn't yet have our postman software in our list of services to remove employees from. This is not Postman's fault. One person had "deleted" all his collections and workspaces after the layoff to clear his laptop of all things related to our company. After we got an email from Postman saying our workspaces were deleted, I removed the laid off users. Since I removed the laid off user, the "trash bin" associated with them was also deleted. Postman support restored all the collections but the "environment" was gone. Which was all of our QA test keys, etc... Our Postman collections are still in shambles after that, and we don't have any employees to manage it anymore. While I totally don't hold Postman accountable - there is definitely a reason why "no-cloud" is a good way to go with these kinds of tools.

sureglymop 3y ago
It makes no sense in the first place for such a tool to even need a login functionality and cloud saves... What's really needed to store information about a few http requests? Maybe a few kilobytes. I never understood it and I particularly don't understand how any company could fall for that. If they instead invested in teaching their engineers how to use curl even that would have paid off more.
- gardenhedge 3y ago
  The benefit of using postman is that you can open the app, see your (shared) collections, easily change the params and hit send. Can curl be used like that?
  - leosanchez 3y ago
    You can use hurl which uses libcurl. You can save it to git and commit your hurl testa in the same repo.
  - soraminazuki 3y ago
    Of course you can. You can use any tool that lets you write down commands, run it, and edit it. Shells, editors, interactive notebooks like Org Mode, etc. The beauty is that it's just text that you can copy and paste between your tool of choice. You're not locked in to a single tool.
    - throwitaway222 3y ago
      It's not very fun to run the auth call, then copy and paste the access token to the next call, and have to update all of your curl cmds all the time... Even if you use env variables, that's a horrible way to use env variables.
      - soraminazuki 3y ago
        You’re making the case for automation, which happens to be something the shell excels at. Use unexported shell variables or command substitution (e.g., “$(pbpaste)”). Directly use the result of the auth call without going through the clipboard if possible. Create a shell script if shell history isn’t enough. Use interactive notebooks if you need something more advanced. The possibilities are infinite.
        throwitaway222 3y ago
        At this point, just write a script Or perhaps write a script that has some kind of GUI. Or maybe make the gui run the URL You're right the possibilities are endless. And this Bruno and postman or permutations of that endlessness.
        soraminazuki 3y ago
        If I understood correctly, you claimed that saving requests, modifying it, or parametrizing it was somehow more cumbersome to do with curl than with a GUI. I was just pointing out that the shell is literally designed for all those use cases. And human users don't interactively use curl without a shell. Also, using curl and the shell allows you to progressively iterate. So "write a script at that point" was kind of the point. Though you don't need to go that far to just feed authentication info. GUI solutions don't have endless possibilities. You start and end with the exact same tool. The clicks and form fillings can't easily be copied around and iterated on unlike commands in a REPL. You can only perform tasks defined by the author of the application.
        gardenhedge 3y ago
deleted 3y ago
[deleted]

sureglymop 3y ago

It makes no sense in the first place for such a tool to even need a login functionality and cloud saves... What's really needed to store information about a few http requests? Maybe a few kilobytes. I never understood it and I particularly don't understand how any company could fall for that. If they instead invested in teaching their engineers how to use curl even that would have paid off more.

gardenhedge 3y ago
The benefit of using postman is that you can open the app, see your (shared) collections, easily change the params and hit send. Can curl be used like that?
- leosanchez 3y ago
  You can use hurl which uses libcurl. You can save it to git and commit your hurl testa in the same repo.
- soraminazuki 3y ago
  Of course you can. You can use any tool that lets you write down commands, run it, and edit it. Shells, editors, interactive notebooks like Org Mode, etc. The beauty is that it's just text that you can copy and paste between your tool of choice. You're not locked in to a single tool.
  - throwitaway222 3y ago
    It's not very fun to run the auth call, then copy and paste the access token to the next call, and have to update all of your curl cmds all the time... Even if you use env variables, that's a horrible way to use env variables.
    - soraminazuki 3y ago
      You’re making the case for automation, which happens to be something the shell excels at. Use unexported shell variables or command substitution (e.g., “$(pbpaste)”). Directly use the result of the auth call without going through the clipboard if possible. Create a shell script if shell history isn’t enough. Use interactive notebooks if you need something more advanced. The possibilities are infinite.
      - throwitaway222 3y ago
        At this point, just write a script Or perhaps write a script that has some kind of GUI. Or maybe make the gui run the URL You're right the possibilities are endless. And this Bruno and postman or permutations of that endlessness.
        soraminazuki 3y ago
        If I understood correctly, you claimed that saving requests, modifying it, or parametrizing it was somehow more cumbersome to do with curl than with a GUI. I was just pointing out that the shell is literally designed for all those use cases. And human users don't interactively use curl without a shell. Also, using curl and the shell allows you to progressively iterate. So "write a script at that point" was kind of the point. Though you don't need to go that far to just feed authentication info. GUI solutions don't have endless possibilities. You start and end with the exact same tool. The clicks and form fillings can't easily be copied around and iterated on unlike commands in a REPL. You can only perform tasks defined by the author of the application.
      - gardenhedge 3y ago

deleted 3y ago

[deleted]