1. Command line UIs are still an order of magnitude easier to build than even the most basic web page.
2. Every app doesn't have to target every user in the world. There is an entire category of developer-focused tooling that is very suitable for the command line.
3. There are plenty of contexts where the command line is the only interface available.
> Command line UIs are still an order of magnitude easier to build than even the most basic web page.
I think by "interactive command-line apps", parent commenter is talking more about "TUI applications" like e.g. `htop` or `vim`- which are persistent/interactive and treat the terminal as an interactive, 2d canvas into which they render the program content. As opposed to what I'd call "normal" CLI applications, which typically render output and expect user input on a line-by-line basis. (Like most REPLs, or the various ctl programs like `kubectl`, `pgctl`, etc.)
2. Every app doesn't have to target every user in the world. There is an entire category of developer-focused tooling that is very suitable for the command line.
3. There are plenty of contexts where the command line is the only interface available.