this post was submitted on 30 Jul 2026
23 points (100.0% liked)

Programming

27909 readers
202 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] slazer2au@lemmy.world 3 points 21 hours ago

We have a custom cross platform CLI tool for managing our sovereign cloud which I use quite a bit. But I cheat as a daily windows user and have Debian installed in WSL.

The only windows specific things I run is route print when troubleshooting our remote access VPN, TNC ( test net connection, I can never remember where the hyphen goes), and our own tool.

Its kinda sad, due to the corporate spyware its faster to launch a WSL console then it is to launch powershell most of the time.