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

Programming

27909 readers
201 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
[–] whotookkarl@lemmy.dbzer0.com 1 points 19 hours ago (2 children)

If I'm on a windows box by order of preference wsl, cygwin, PowerShell, console. There's no package manager so I use either chocolatey or the cygwin packages.

[–] CalcProgrammer1@lemmy.today 4 points 19 hours ago

There is winget, which is built into newer Windows. You can install a decent amount of stuff using it. I have a setup script for setting up my OpenRGB development environment that uses winget to pull down MSVC build tools and libraries, 7-zip, and more.