I have what I think is a somewhat contrarian view among programmers: the CLI is NOT the world's best interface for most things. It CAN be efficient with decades of practice (which I have). But for all the dogma of CLIs just being "better," I still haven't found a sane way to curl a URL with Korean text in the query string. I have to encode the URL first! This is UX, and is solved in nearly every GUI.
Text may be the "universal API" but all that means is that it's the lowest common denominator.
=> More informations about this toot | More toots from ianthetechie@fosstodon.org
@ianthetechie Okay, I'll bite 😀 What's an example of a Korean string you might want to query?
=> More informations about this toot | More toots from duncan_bayne@bsd.cafe
@duncan_bayne The rant-of-the-day is motivated by me testing a geocoding API over HTTP, and one of the things I wanted to verify was that some Korean test cases worked. But since I can't just type Korean into the terminal without urlencoding, the easiest way is actually to ssh port forward and use a graphical tool like Postman, or even a web browser to make the request. Just about everything besides the shell will handle this correctly.
=> More informations about this toot | More toots from ianthetechie@fosstodon.org
text/gemini
This content has been proxied by September (ba2dc).