[deleted]
Comment on When the Category Leader Stalls : Postman and the Future of API Tooling
expr@piefed.social 4 days ago
Comment on When the Category Leader Stalls : Postman and the Future of API Tooling
expr@piefed.social 4 days ago
Wrong comment to rely to?
dhruv3006@lemmy.world 3 days ago
Curl is great. I use curl. Most developers use curl. But “you can call an API with curl” and “curl is enough as an API working environment” are two very different claims.
The problem is that real API work is almost never just one request typed into a terminal like some kind of beautifully minimalist Unix haiku. It usually turns into auth, environments, copied headers, reused payload fragments, request chains, documentation, testing, debugging, sharing examples with teammates, reviewing changes in Git, and trying not to break prod because you forgot to swap one token or one base URL.
At that point, people are not really using “just curl” anymore. They are using curl plus shell scripts, plus notes, plus env files, plus copied commands from Slack, plus random JSON files, plus tribal knowledge. Which is fine, until it becomes annoying, fragile, and weirdly hard to collaborate around.
That is the gap api clients like Voiden is trying to solve.
So for me it is not “curl vs Voiden.” curl is a low-level execution tool. Voiden is a workspace for actual API work: writing requests, organizing them, reusing pieces, documenting them, testing them, versioning them in Git, and not duplicating the same headers/body/auth setup 45 times like a person slowly losing control of their life.
AA5B@lemmy.world 3 days ago
That all sounds like a nightmare. I use curl api calls from DevOps where I’m not really doing much and time isn’t usually a concern. But I can’t imagine our product developers using it, it just doesn’t seem scalable, maintainable or performant
expr@piefed.social 3 days ago
This argument doesn’t really hold up, honestly. That is all easily done with shell scripting, and shell scripts can be committed to source control and shared to other members of the team easily. This is what my team does for our common API needs. It even has ecosystem support in many places, such as popular openapi renderers providing curl command examples for routes automatically, being able to copy the exact request made by a web browser as a curl command from the network tab automatically, and so on.
I use curl for absolutely everything, including testing out my work for each and every ticket I work on. Been doing this for years now. It works great and has many, many advantages over property bullshit like Postman.
dafalcon@lemmy.world 3 days ago
I think both of you are right, just talking about slightly different layers of the problem.
curl absolutely works (and it rocks!). Shell scripts absolutely work. For terminal-native teams, that can be a great setup.
But this feels a bit like two very old debates mashed together: terminal/Vim vs Git GUI, and Emacs vs IDEs. Yes, some people are perfectly happy doing everything from primitives - git in the terminal (i hope by the majority), editing in Vim, wiring things together with scripts, maybe extending Emacs until it becomes a small civilization :D. That is a real workflow, and for the people who like it, often a very effective one.
But the existence of that lower-level workflow does not make higher-level tooling pointless. It just means different people and teams want different layers of abstraction on top of the same underlying capability.
So I do not think the real question is “can curl do it?” it can, for sure!. The real question is whether raw requests plus scripts are the best shared working model once API work starts involving reuse, documentation, onboarding, review, collaboration, and people outside the terminal-native crowd. For some teams, yes. For many teams, not really.
That is where something like Voiden, starts to make sense to me. Not as a replacement for curl (at the end they are all making a simple API request), but as a way to make API work more modular, composable, and shareable without everything turning into a pile of scripts, copied commands, and scattered docs.
But the bigger problem i see is when simple tooling (or rather what should be simple) become super bloated - and are super opinionated and take away the flexibility from users - and they end up having to design their workflows around how a tool works. Voiden i guess is taking the less opinionated stance - and trying to give all the freedom - with markdown, offline and programmable interfaces etc etc… but let’s see.