From: W B Hacker <wbh@conducive.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] what a surprise
Date: Sat, 5 May 2007 11:06:03 +0800 [thread overview]
Message-ID: <463BF49B.3030208@conducive.org> (raw)
In-Reply-To: <1685338d0ad2e3851df8cd33ddbb1de4@quintile.net>
Steve Simon wrote:
>> In particular, to be at all effective with rio (and especially acme)
>> you need to be a capable command-line user and understand how to
>> compose those primitives.
>
> I think this is true, however I do think there is a class of user who writes
> applescript macros and Windows BAT or even VB who can relate to rc scripts
> and acme/sam/rio.
>
> Mainstream computer users who can appreciate the plan9 GUI environment are
> not common but they do exist.
>
> -Steve
>
Counterpoint:
I'll take the first as stipulated - IF qualifed with:
'... and have learned in, or adapted to, the acme/rio environment.'
IOW 'the appropriate sort of' capable CLI user..
But IMNSHO, the exact opposite applies to paragraph two!
- the more familiar with *any other* CLI environment, (possible exception of
Oberon/Aos) the *more difficult* it is to adapt to acme/rio.
Or to accept the need to do, or value of, so doing. It just isn't immjediately
obvious as to WHY SO.
A person with no significant CLI 'habits' to alter/unlearn would generally have
an easier time learning acme/rio from a cold start than your exemplary
'exeprienced' CLI'er. As was once the stregth of a Mac vs a 'pee sea'.
Too much to 'shed' before learning a new paradigm.
I don't think acme/rio vs, for example the comparably text-based, cut 'n paste
to-execute 'commands-from anywhere usage' in native Oberon / Aos are anywhere
near as different as Chinese and English (which are processed by entirely
different parts of the brain - written OR spoken)..
BUT .. the *apparent* 'wrong handedness' of acme/rio vs 'all others' is a
barrier, even to natively ambidextrous folk (ich).
Learning 9'ish mouse-chording and the rest of acme/rio just to explore 'plumber'
and such may constitute as important and necessary step to a better productivity
'fit' for Plan9 [1] as adapting to RPN was for forth ... but barrier these are
to the newbie.
As with Chinese, English, Arabic, or Finnish - small children seem to have no
problem learning at about the same age. So it isn't about what we can or cannot
learn, or even about works or doesn't work.
It is about what best fits the local environment.
;-)
JM2CW
Bill Hacker
[1] I have come to view acme/rio & chording as an IDE suite specific to
productive 9'ish devel - on which score I am not able to fault it - nor care to try.
next prev parent reply other threads:[~2007-05-05 3:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 19:17 ron minnich
2007-05-04 19:32 ` erik quanstrom
2007-05-04 19:32 ` Paul Lalonde
2007-05-04 19:43 ` lucio
2007-05-04 19:58 ` Russ Cox
2007-05-04 20:07 ` lucio
2007-05-05 2:37 ` Kris Maglione
2007-05-04 22:47 ` Steve Simon
2007-05-05 3:06 ` W B Hacker [this message]
2007-05-05 5:08 ` Bruce Ellis
2007-05-05 19:08 ` erik quanstrom
2007-05-05 19:19 ` lucio
2007-05-05 21:13 ` W B Hacker
2007-05-06 20:10 ` Roman Shaposhnik
2007-05-06 20:28 ` Federico Benavento
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=463BF49B.3030208@conducive.org \
--to=wbh@conducive.org \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).