What to do after Python?

[Sheila King]

I realize that you were writing this, all tongue in cheek, but a newbie who
asked the original question, might not pick up on that. The next thing you
know, he will be asking, "What are registers?" and wondering why he should
know how many a machine has.

--
Sheila King
http://www.thinkspot.net/sheila/
http://www.k12groups.org/


On Sun, 18 Feb 2001 14:13:58 -0500, Roy Smith <roy at panix.com> wrote in
comp.lang.python in article <roy-6DE44A.14135818022001 at news.panix.com>:

:Actually, the problem with C is that it hides too much of the computer 
:behind all that code.  I spent a few years writing C on alphas, and never 
:even found out how many registers the danged thing had.  If you really want 
:to find out what the hardware is all about, learn assembler, which is 
:perilously close to handing a soldering iron to a software guy.
:
:Another alternative would be to learn lisp.  It may not get you a better 
:job, but will give you the ability to write a better python major mode for 
:emacs :-)
:
:I don't suppose I could interest you in fortran?