22 Nov
2007
22 Nov
'07
5:07 p.m.
--- Chuck Guzis <cclist at sydex.com> wrote:
For some, that's not sufficient. Understanding
how
a disk drive
works or what goes on over a TCP/IP connection is
essential to them.
TCP/IP is one thing. But knowing how a dd works
today?? If you're writing i/o it's one thing.
Otherwise phew.
Beginning with a battery and a lamp, then moving to
experimenting
with semiconductors, then developing logic elements
and finally,
understanding the "guts" of a computer creates a
depth of
understanding upon which to build.
So my vote is for starting simple and building.
If my opinion matters, it's a little too intense from
the get-go. I'd concentrate on the *vagueries* of ic's
and work down as necessary. Even w/assembly language,
just how much of what goes on at the gate level is
useful? Few, make that precious few have any clue what
goes on in a uP at the level you're talking about.
Sure it would be great for a kid/? to learn how to
build a discrete logic cpu. But that's an awfully
specialized area of computing for most of us.
Amidst the ensuing cries of treason or the like, a
lot of people feel that entering opcodes in hex on a
keypad is a tad *tedious* (polite version). Different
strokes for different folks I guess though. How many
people actually need to program in assembly language
these days?? As time progresses, a lot of the
knowledge that was essential in earlier times will
cease to be a necessity. I know the original question
was posed on a vintage list, but is it necessary to
learn on an 8-bit unit? There may be some good reasons
to, but if at all possible learn on something that's
going to be more relevant to today's environment (and
even that's a stretch in the case of an early pc).
____________________________________________________________________________________
Be a better sports nut! Let your teams follow you
with Yahoo Mobile. Try it now.
http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ