the kind of programming compy eng people will do would probably
be of a lower level (architecturally speaking) than the programming
pure compy sci or software eng people will do .....
lower level stuff like kernel programming, writing device drivers
etc (that means lots of C, C++, some scripts) ...... if you like
such things, take compy eng, .... else take pure compy sci ....
where you'll probably be working higher up the abstraction tree
(higher level languages, java, C#, prolog, etc ) ... you'll get to
hack kernels in compy sci of course, but as a rule you'll deal more
with the software side of the abstraction ....
but I regretted not going into compy eng though .... to be honest,
I think it's a better option career wise, not that I enjoy kernel
or OS programming (*cringes ... )
