On Apr 30, 2010, at 12:14 , John Sessoms wrote:
From: John Sessoms
I don't consider it such a "obvious troll line". Learning to deal
with a command line wasn't that hard. It was a bigger deal
regaining speed when the GUIs took over. What I used to be able to
do with just a few typed commands now took a lot longer opening and
clicking menus. Especially with the overhead of painting the screen.
I know it's stupid answering my own post, but there were some things
I left out.
In DOS I could write batch files to handle repetitive tasks. I never
quite mastered programming for the Windoze GUI, with all the
overhead necessary to open & close windows turn everything into menu
selections add in the necessary widgets ...
And Windoze was enough of a pain I never even cared to ATTEMPT the
Mac.
Here I can agree with you both. The CPU was not quite up to speed for
a GUI system when Apple introduced the Macintosh in 1884. It was more
than a decade before both the Mac OS and Windows got enough hardware
underneath them to make the GUI overhead transparent and pleasantly
reactive.
I personally stopped writing machine code when the Mac came out, as 32
bit was just more than I wanted to devote my time to playing around.
And I never really learned any of the many programming languages
popping up to a depth that I could do much more than hack at them,
usually unsuccessfully. Even though I appreciated the runtime routines
that were then known as calls made it fairly easy to get something
running, in my mind this was the beginning of "bloatware", something
I've always been dismissive of. Don't know how to do it, and I
understand the down-side economics of writing everything in machine
language, so I (we) must live with it.
Joseph McAllister
Lots of gear, not much time
http://gallery.me.com/jomac
http://web.me.com/jomac/show.me/Blog/Blog.html
--
PDML Pentax-Discuss Mail List
[email protected]
http://pdml.net/mailman/listinfo/pdml_pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow
the directions.
