Hey that’s not fair, plenty of them also know how to upload hardcoded secrets to postman.

The same guy that parses JSON by hand (rather than use a library)

Of course I know him. He’s me.

Or a past version of me anyway that was too dumb for its own good and also tried to do datetime stuff and several other complex things. Daft moron, that guy. Glad I don’t have to work with such idiots any-

Looks at coworkers

Glad I can now look down on such-

Looks at own work

You know what, never mind.

I really like that the link at the bottom of the page says “check out more stuff you should be using” but that URL takes you to a page where the curl article is the only link.

“more coming soon. Or not. I don’t owe you shit”

A majestic site indeed. Bravo sir.

The low-tech version of it is that there is a certain technical way of asking computers for stuff, usually across the Internet. To do that as a human, for instance to build a system that can ask or answer these questions, there are a few different tools.

One is Postman, which is a fancy, graphical tool that essentially loads a full browser for interacting with parts of the question, sending it and displaying the answer. Of course, it’s a commercial product, so some nice features are locked behind paywalls. The full browser also requires more memory and more time to load.

Another is cURL (alias curl), which is a command line tool, meaning you just enter the various parts of the question as text. It’s a little less convenient for more complex questions to remember how to specify the question’s parts and adjust them, because instead of a nice table where you enter them, you have to type it in text, but you can use various other features of the command line to make it easier for yourself. In some cases such tools may have advantages over the graphical ones, allowing you to do things the other can’t do (or at least not easily).

The whole page is a rant about people using the heavier and commercial graphical tool instead of the lighter and freely available command line tool. It’s a tongue-in-cheek continuation of an old argument in some software developer circles, where you will have people who prefer to use certain graphical tools and others that not just prefer command line tools (or generally text-based code), but also feel like everyone should just use them instead. For some, that’s just friendly banter. For others, it’s a deeply ideological conviction.

Personally, I’d suggest that people use whatever works for them and their team. For example, I have little choice but to use a mostly graphical tool because I work together with people who don’t have the time to learn the text-based options. They might be a great tool for me, but if my work is unusable to others, that makes it harder to work together (and accordingly means that I’d be stuck doing everything myself, which I frankly don’t have the time for).