On 2017-08-08 22:27:29 +0000,
onewing...@gmail.com said:
> On Monday, August 7, 2017 at 7:41:16 PM UTC-6, Arne Vajhøj wrote:
>> On 8/7/2017 12:29 AM, onewingedshark wrote:
>>> On Thursday, July 20, 2017 at 6:45:38 AM UTC-6, VAXman- wrote:
>>>> My kid got his hands on Linux. He played about with it and he got many
>>>> things working -- much to my surprise -- but he lost initiative when he
>>>> had to spend too much time typing to interface with it.
That's the typical response most folks to that style of user interface,
and a response that should be very familiar. Younger folks can be
smart about this, having grown up swimming in computers and software
and good and bad user interfaces.
Many of the business folks using computers do unfortunately deal with
some pretty bad user interfaces — command line, SMG/curses/ncurses, and
more than a few internal-use GUI apps for that matter — and they use
those interfaces because they get paid to. That's a budget shift from
the internal app developers over to the end-users and the trainers and
support folks for the business, too. Sometimes that works. Sometimes
not.
Taking a different tact with these same design and complexity issues
around user interfaces being difficult and expensive to modify, one of
the tool chains I deal with has split off the GUI design and
implementation and making it entirely feasible to substantially alter
the GUI with minimal or no changes to the application code, too.
>>> To be fair, Linux is terrible when it comes to usability mnemonics --
>>> ls, ld, ar, and so on are terrible names when it comes to human memory,
>>
>> Why? They are abbreviations of what the commands does.
>
> Terrible abbreviations: generally two letters of some functionality
> that was generally more recognizable by a different name [at that point
> in computing; the popularity of unix-like OSes has altered terminology]
> isn't conducive to memory.
Though we're far past the era of anybody using the command line outside
of the folks that really need to, and there's a fairly large overlap of
those same command-line folks with folks that are programming in one or
more languages in addition to the shell. And the vast majority of
those command-line folks either know bash (or zsh, fish, or some other
shell), or they know PowerShell and the DOS-box, or both. Fewer know
DCL. And more than a little scripting code that runs in those other
command line environments, and a whole lot less that runs in DCL. Not
that DCL will ever go away on OpenVMS, at least not before somebody
writes the tools necessary to translate it into whatever replaces it
and likely not even then.
Complaints of the current command line morasses aside, any (potential)
replacement for (for instance) bash or fish shell or otherwise is going
to have to run far more widely than OpenVMS, or OpenVMS usage will have
to expand at ludicrous speed. PowerShell runs on other platforms now,
for instance. This if DCL or some unspecified DCL replacement is ever
going to be anything more than a platform-specific curiosity.