News for hackers. Stuff that matters.
Re:Command Line Interface Guidelines by ojintoad on Tuesday February 06, 2024 @01:16PM (#39278137)
Agree!

I'll go further. PowerShell covers a lot of the concerns in the OP out of the box. It is extremely well thought out and is one of my favorite cli models to buy into.

Re:Command Line Interface Guidelines by bigstrat2003 on Tuesday February 06, 2024 @02:42PM (#39279472)
Powershell is just plain a great shell. Blows all the *sh variants out of the water. I'd love for it to gain traction in Linux (so that, for example I could use it as my shell on my desktop) but I don't really see that happening.
Re:Command Line Interface Guidelines by partdavid on Wednesday February 07, 2024 @12:52PM (#39291705)
What are the things that are stopping you?

I use MacOS on my personal machine and Linux for various shellboxes and I switched to Powershell years ago and haven't looked back. Occasionally I invoke bash as a language runtime for checking shell script stuff, the way I would any other language's REPL, but for a shell? Powershell is strictly better.

The one actual problem with Powershell in this area is quoting for external commands. It's solvable in scripts by replacing certain things with double-quoted equivalents but not really interactively, and it is an occasional pain (though I still think it's overall less of a problem than quoting in general in bash and its ilk).