Joe_Luzzi.FULLERTON_CC@QMBRIDGE.CALSTATE.EDU (Joe Luzzi) (04/08/91)
Time: 10:24 AM
Date: 12/21/90
Subject: Re: Re- HLLs vs. Assembly
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>That's commendable, but that's not what RHyde was saying. He was
>>maintaining that applications generally SHOULD be developed in assembler.
>>If somebody applied for a programming job here and indicated that he
>>planned to use assembler to accomplish most of his assigned tasks, I can
>>assure you he would not get the job.
I understand Randy's point. He is not saying BURN HLLs, he's merely trying to
state that there are applications for certain hardware that would perform
better if written in Assembly. Assembly may be choosen because there aren't
any efficient compilers available for the particular platform you're
programming for, and speed is desired.
My point (brought about by Randy's comment on teaching assembly):
I don't think anyone who applies for a programming job sets conditions such as,
"I only program in assemlby." Knowledge of HLLs is a skill programmers must
have, but I believe knowledge of assembly is just as important. You compare
programmers who just know HLLs to those who know HLLs and Assembly, and you'll
find the latter to be a better programmer.
Here is proof:
>>This is very important when doveleping software. One person I work with
>>doesn't even know what assembly is (she barely knows what a HLL is either).
>>I have to spend half of my time at work explaining to here why something
>>will or won't work because she knows nothing about the limitations of the
>>machine. Also, another person I work with just graduated with a degree in
>>computer science. Computers are his life. He knows all about HLLs but he
>>doesn't understand why alot of things work or why they don't work, because
>>he doesn't understand assembly language or the limitations of the hardware.
>>Computer Science courses should begin with explaining computers from the
>>bit level and working their way up. By the time the students get to the
>>HLLs, data structures, files, etc..., they should have virtually no
>>problems undterstanding those concepts and how they came to be, and what
>>the limitations are.
>>BITNET-- mquinn@utcvm <------------send files here
>>pro-line-- mquinn@pro-gsplus.cts.com
Exactly the point I'm trying to make. It's not that you're going to be doing a
heavy amount of Assembly in industry, but the knowledge you gain having learned
Assembly language programming is a valuable asset.
I also don't cringe at the mere mention of the word "Assembly" because I'm not
afraid to program in it. If I were a respective employer and interviewed
applicants with Assembly langauge knowledge, while I wouldn't necessarily
require it, I'd probably be more apt to hire these individuals. My company may
only rarely use assembly, but I'd know that these applicants who learned
assembly would have an edge that would be relected in the programming tasks
they performed ( whether it be in a HLL or Assembly).
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Joe M. Luzzi
Internet: Joe@CSU.FULLERTON.EDU
BITNET: LJMLUZZ@CALSTATE.EDU
GENIE : JM.LUZZI
AOL : JMLUZZI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=