Linked by David Adams on Fri 5th Aug 2011 17:42 UTC
Graphics, User Interfaces Since we're on a CLI kick today, here's an "attempt at presenting some of the most important guidelines for CLI design."
Thread beginning with comment 483942
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Gawd awful guidelines ...
by shotsman on Sat 6th Aug 2011 17:56 UTC in reply to "Gawd awful guidelines ..."
shotsman
Member since:
2005-07-22

To paraphrase a character from 'Little Britian'

Yes. But No But Yes But...

There has been an alternative to the Unix shell that has been around 30+ years.
As you sat, no one is going to get RSI from using

copy/log

instead of

cp -v

But it goes way beyond this.
The Unix shell is as pretty well everone agrees a powerful tool. So is the VMS DCL Shell.
Both have their +ve's and -ve's.
However in 30+ years of using both, the DCL shell is far more natural and is a pleasure to use.
Now I am the first to admit that people moving to it from Bash etc are mystified by it.
Once you reset your perceptions it becomes perfectly logical.

What I'm trying to say is that was can do a lot better than the Unix shell.
I agree that using it as a reference point in CLI design is just plain crazy.

I'd expect that if you asked this question of the original Unix devs they'd give you the country mile answer.
viz, 'I wouldn't start from here'.

It is a pity that more people aren't interested in moving the CLI forward.

Reply Parent Score: 2

moondevil Member since:
2005-07-08

Lately I have been using Powershell and it is quite powerful, by merging Unix concepts with .Net and object pipeline.

Might have its quirks, but it sure is way lot better than using command.com or cmd.exe.

Reply Parent Score: 3

foregam Member since:
2010-11-17

I wouldn't call it pleasure. It's more consistent, yes (e.g. only one way to pass options) but highly unorthogonal too. SET and SHOW are the best examples — it's the same old idea "let's make it feel like English" that begat COBOL.

Reply Parent Score: 1

moondevil Member since:
2005-07-08

Actually my two issues with Powershell are the stupid ps1 extension even for Powershell 2.0 scripts, and the way you need to sprinkle your code with .Net annotations when creating scripts.

I use it as a better shell that is Windows native, but when the time comes to write scripts I prefer Python or F#.

Reply Parent Score: 2