Being able to choose is a good thing. Use what works for you. I prefer the terminal, but not as hard core as switching to a TTY and never see a GUI again...
> Being able to choose is a good thing. Use what works for you.
If you look at many of the ‘user stories’ in this thread (and others), you see a lot of people using vi/vim not because they decided to try it, but because they had no real choice. Very often it’s the only usable option on a Unix-like machine.
And yet, you don’t see many people bemoaning the choice. Despite being forced to use it, once people are over the fabled learning curve they tend to like it.
I meant the separation of powers between the executive, legislative and judicial branches. Maybe this is more of a thing in Europe, even if not perfect here.
1. from isolation pov, Matchlock launch Firecracker microvm with its own kernel, so you get hardware-level isolation rather than bubblewrap's seccomp/namespace approach, therefore a sandbox escape would require a VM breakout.
2. Matchlock intercepts and controls all network traffic by default, with deny-all networking and domain allowlisting. Bubblewrap doesn't provide this, which is how exfiltration attacks like the one recently demonstrated against Claude co-work (https://www.promptarmor.com/resources/claude-cowork-exfiltra...).
3. You can use any Docker/OCI image and even build one, so the dev experience is seamless if you are using docker-container-ish dev workflow.
4. The sandboxes are programmable, as Matchlock exposes a JSON-RPC-based SDK (Go and Python) for launching and controlling VMs programmatically, which gives you finer-grained control for more complex use cases.
I've done "being not only a developer" for some time. It's okay, even fulfilling but sometimes exhausting. Would have liked to take a break at some cushy, technical only position. Damn, should have done this while still possible...
Question: Do I miss something by not using Postman? My alternatives for development are "Edit and Resend" of a request (in Firefox) and plain old curl scripts for reusable examples.
Not Postman specifically but a client like that will allow you to prepare a whole set of different requests and save them so you can build up a test suite, plus some of them do things like scripting, chaining requests together etc. It's like the difference between a text editor and an IDE, so it depends on your needs really.
I use a mix of tools, depending on needs: `curl` scripts for things I might need to automate on barebones OS installations (Linux/macOS), HTTPie on my local CLI env if I'm debugging something where I need to mutate parameters quickly: making sequential calls, many requests with varying parameters; and Insomnia as GUI where I can save requests with parameters, headers, etc. to be re-used during development.
Each one has its strengths, and weaknesses, Insomnia can export the saved requests as `curl` commands so it's a nice visualisation to iterate over a complex call until it's working, and then be exported if needed to be automated; `curl` is quite ubiquitous but clunky to remember the exact arguments I might need; HTTPie has a nice argument syntax so it's quite readable to be quickly edited but isn't present without installing Python, pip, and pulling it.
We use it a bit at our company. We have a collection file that includes a ton of requests with headers and body. Developers can with ease load that collection file and run it against their own server, and also quickly change to a different server with just a click.
I guess a substitution would be a git repo with curl scripts and environment variables?
We also have some non-tech people who use postman to run tests.
I used to use postman, before they become greedy, now I use Bruno.
But to your question - I have saved based authenticated request to our company useful APIs - github/jira/artifactory - so when I want to string together some micro tool to do something in batch, I don't have to remember where do I create API key, and how do they accept it.
We use it at my work because one team will create the backend, and another team will create the frontend, and its useful to be able to share a big list of all the endpoints, along with how to use them and the expected result that can all be run, as well as handling all the auth for you
At the end of the day with Postman you wind up trying to codify requests via collections, which tends to just be programming in a more limited language.
Just to nitpick on the example: When a trusted or frequently used webpage is bookmarked, search can be restricted to those bookmarks with `*` in Firefox and with `@bookmarks` in Chrome.
reply