Re: Great SWT Program
- From: blmblm@xxxxxxxxxxxxx <blmblm@xxxxxxxxxxxxx>
- Date: 19 Oct 2007 15:55:48 GMT
In article <7IWdnXIf38aBMYXanZ2dnUVZ_rKtnZ2d@xxxxxxxxxxx>,
Lew <lew@xxxxxxxxxxxxx> wrote:
blmblm@xxxxxxxxxxxxx wrote:
In the right frame of reference I claim it all makes sense and
feels reasonably consistent. Apparently it's difficult for
someone accustomed to Windows-style programs to view things in
this frame of reference.
A person would have to be willing to adopt the frame of reference.
Unwillingness to do so, for any tool, will block mastery of that tool. The
proper argument there is not for a flaw in the tool but for the right to
choose not to use it.
Is this where I say again that I'm not arguing that vim is what
everyone should use to edit text [*], only that it's a good choice
for some people? and that I've been continuing to argue because
I have the sense that my opponent, so to speak, isn't willing to
make that concession about his preferred platform/tools?
[*] emacs users are specifically exempt. We need to put aside the
religious wars of the past and ally against the common enemy!
[ snip ]
Probably once or twice a year I do spend, oh, maybe an hour or
two, learning something new about one of my old favorite tools,
or learning a new one. Usually I think this pays off in future
time savings, but maybe it's just a pleasant occasional distraction
from what I'm supposed to be doing. <shrug>
Love of learning for its own sake reaps huge pragmatic rewards. It is good
that you are neither closed to new experiences nor locked in to static
understanding even of familiar tools. As martial arts teachers and most, if
not all, sports coaches emphasize, one should always return to and practice
the basics.
I've been told often that the proper response to kind words is
"thank you" rather than argument. Still ....
You may be giving me more credit than I deserve, since I'm starting
to be all too aware that my continued resistance to mastering [*]
that new-fangled stuff with menus and icons is not a smart career
move. <shrug>
[*] Another point I've been trying to make in this thread is that
there *is* some effort needed, at least for some of us. "Intuitive"
is in the mind of the beholder ....
Then again, if you're doing something with a GUI that involves
file saves, is there really much useful you can be doing while
waiting for the save to complete?
Yes, particularly in the case of autosave. Or you could compile while saving;
you know the memory image matches the current form of the source and you can
ignore that the file copy isn't quite yet the same.
Ah. Yes, quite. I hadn't thought about compiling being done using
data in memory rather than from files .... I wonder whether this
could be somehow related to the weirdness I sometimes notice with
Eclipse, where it shows bogus errors that magically disappear
when one does a "save" or "save all". Hm!
--
B. L. Massingill
ObDisclaimer: I don't speak for my employers; they return the favor.
.
- Follow-Ups:
- Re: Great SWT Program
- From: Lew
- Re: Great SWT Program
- From: Bent C Dalager
- Re: Great SWT Program
- References:
- Re: Great SWT Program
- From: nebulous99
- Re: Great SWT Program
- From: blmblm
- Re: Great SWT Program
- From: Lew
- Re: Great SWT Program
- Prev by Date: Re: static initialization of arrays
- Next by Date: Re: Great SWT Program
- Previous by thread: Re: Great SWT Program
- Next by thread: Re: Great SWT Program
- Index(es):
Relevant Pages
|