Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Anecdotal evidence here. My use-case needs some UI, but a full blown GUI is way, way overkill.

I am building tooling around "Verifiable Credentials" (the W3C standard, OpenID standard, and all the standards around and below it).

So me and my co-workers need tools to check JWTs, resolve DIDs, generate Proof of Possession, .well-known contents and services discovery, do OpenId Connect flows, interpret "offer requests", "presentation requests", QR-codes, etc. It started as a bucket of random commandline things that random devs whipped up when needed (in typescript, python, bash, rust, some PHP), and now slowly consolidated into a consistent "toolkit". I am currently still porting most of these tools to Rust and make their CLI interface and IO consistent.

But from there I'll be adding a TUI very quickly.

By no means meant as "end-user" software - those exist and called "wallets". But for developers and devops working in this niche. These don't need a GUI. I'd even wager these users don't want a GUI but prefer a TUI, but in any case, the TUI is just so much easier and more accessible for me as a dev that it's the choice between a TUI+CLI or no UI, just CLI.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: