What to do after Python?
Roy Smith
roy at panix.com
Sun Feb 18 14:13:58 EST 2001
More information about the Python-list mailing list
Sun Feb 18 14:13:58 EST 2001
- Previous message (by thread): What to do after Python?
- Next message (by thread): What to do after Python?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
cg at cdegroot.com wrote: > I'd advise C as a second language because it forces you to deal with the > computer behind all that code, which tends to give you a good > perspective for other language. 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?
- Previous message (by thread): What to do after Python?
- Next message (by thread): What to do after Python?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list