51–60 of 73 posts
> "To that end, configuration is defined in a YAML file called the request collection" Genuine question, why do people use YAML? I've been using it a little bit recently (reading existing documents, not writing my own), and it just seems like a more overcomplicated and less human-readable version of JSON? With potential security vulnerabilities?
https://opensource.posit.co/blog/2026-05-21_in-defense-of-ya...
looks nice when you want to quickly get something up and running! i'm trying to move away from GUI-based, and i haven't really found a nice workflow with just using curl https://justuse.org/curl/
These small utilities are great, now so quick and easy to create. I made a TUI version and then grew tired of it and ported it to Electron, took less than an hour for each. For those complaining about YAML format, you can create your own in less than an hour using whatever format you want. The potentially disheartening thing about the ability to create apps like this, they are just low effort are they even worth shar…
For those who are using Emacs, https://github.com/federicotdn/verb provides similar UX, I have been using it as a postman alternative for quite some time.
Postman has turned from something that's bad, that I put up with, to something that's god awful that I simply refuse to engage with. Now days, I just do everything with curl, shell functions and history
This has been extremely helpful... I'm as inclined to copy as fetch then paste and tweak in a TS file as I am to use curl or anything else... I've pretty much stopped using things like postman altogether.
Earlier quoted context omitted.
YAML: - - "hello" YAML expanded: - - "hello" JSON (typical formatting): [ [ "hello" ] ] And EDN for good measure: [["hello"]] I know which one I prefer :) Silly example perhaps, but once you have X lists nested in Y lists, it does become a lot easier to see why some prefer a bit more visually hierarchically stronger syntaxes
I still prefer ini files for configuration. Easier to grep and sed.
looks nice when you want to quickly get something up and running! i'm trying to move away from GUI-based, and i haven't really found a nice workflow with just using curl https://justuse.org/curl/
I used to write Python scripts with Requests or run from terminal. It has a nicer syntax, all LLMs know it, and we all used Python in the backend. https://docs.python-requests.org/en/latest/index.html
TUI stands for "Text User Interface" not "Terminal User Interface" considering that the point of TUI vs GUI is to distinguish text mode from graphical mode. The word "terminal" isn't really meant to imply text even if quite a few terminal emulators are, indeed, text mode; rather it typically means that the UI is drawn by some other machine than the one you're touching. For example, a very popular Windows Server featu…
The distinction we (Ratatui) draw is that the rendering surface is a terminal: historically sometimes a physical hardware terminal (someone got Ratatui running on a Minitel a while back), more commonly today a terminal emulator/PTY environment.
That framing also better captures the kinds of constraints and capabilities Ratatui apps actually deal with: terminal escape sequences, cell-based rendering, alternate screen buffers, mouse handling, resize behavior, scrollback interaction, etc.
In addition, these apps don't only do text only these days as modern terminals support various graphics protocols (Sixel, Kitty, iTerm graphics) and other extensions that can allow for weird and wonderful things that are not just text.
There is also the term CHUI for Character User Interface that is contrasted with TUI.
Earlier quoted context omitted.
I still prefer ini files for configuration. Easier to grep and sed.
They work wonderfully until you need to do anything more advanced than a key-value store.