I built a service whose primary client is a CLI program. I was thinking about building that client for Windows as well (not just WSL). My target users are generally technically-proficient so I’d rather not build a whole GUI app if it’s unnecessary. But I honestly have no idea how often Windows users use CLI tools beyond some Windows admin stuff.

So if Windows is your daily driver, how often do you leverage the shell and how unusual would it be to use CLI tools in your workflows?

  • As a programmer, I use it all the time. But I’ve seen IT students saying they are “scared of the console”. And many devs seem to be scared of git and just merge everything somewhere somehow without ever looking at a git graph. Of got target audience is programmers, CLIs should be fine. If not, then it depends on more details. Can you tell more about the service/application?

    • treadful@lemmy.zipOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 day ago

      I built a service for people to create simple Web sites using Markdown and CSS (jot.run) and the primary interface is currently a CLI client. So the target audience will be comfortable with those simple formats at least. So maybe not only programmers, but probably only technically-oriented people.