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 484009
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Gawd awful guidelines ...
by foregam on Sun 7th Aug 2011 17:54 UTC in reply to "RE: Gawd awful guidelines ..."
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

foregam Member since:
2010-11-17

I was referring to DCL, not Powershell. Maybe I'm a bit unfair and what I actually don't like is VMS underneath DCL. I definitely don't like its kitchensink philosophy, though I'm impressed as hell by its stability, security features and clustering capabilities. OTOH OpenBSD has those too, in addition to a much saner environment.

Reply Parent Score: 1