Most Annoying csssm posts
in [Matlab]
|
Prev: Calling .NET from MATLAB
Next: Image Averaging
From: Peter Boettcher on 14 Sep 2006 16:31 "Duane Hanselman" <masteringmatlab(a)yahoo.com> writes: > Here's a list of most annoying cssm posts. (Started in a different > thread.) Please add yours as well as suggested replies. I'd like to > keep this around so annoying posts can get quick "cut and paste" > answers. This stuff should probably be incorporated into the FAQ, then people can just post a link to the appropriate answer. I know, I know, it's been a very long time since I've updated the thing. I want to find a Wiki to put it on, and I'm a little reluctant to use the one TMW has offered me. That is what will happen to it soon, though, unless someone else can help find a Wiki site of some sort. -- Peter Boettcher <boettcher(a)ll.mit.edu> MIT Lincoln Laboratory MATLAB FAQ: http://www.mit.edu/~pwb/cssm/
From: Steve Amphlett on 14 Sep 2006 17:22 Rune Allnor wrote: > > > Well, this is one of many "pet peevees"(?). My first professional > degree (BSc) was as a computer engineer. The first three semesters > were spent learning the 8086 virtually on the shift regisetr level. > The next two were spent learning the 286. Then the 386 was > released and I decided that I had better ways of spending my > time that learning a new microprocessor every six months. Damn! I thought I was a youngster here. My first JOB involved 6502 programming. Counting clock cycles etc. Oh well, time to give it up to the new kids.
From: Roger Stafford on 14 Sep 2006 18:00 In article <1158259215.915274.233250(a)m73g2000cwd.googlegroups.com>, "Rune Allnor" <allnor(a)tele.ntnu.no> wrote: > ..... > Well, this is one of many "pet peevees"(?). My first professional > degree (BSc) was as a computer engineer. The first three semesters > were spent learning the 8086 virtually on the shift regisetr level. > The next two were spent learning the 286. Then the 386 was > released and I decided that I had better ways of spending my > time that learning a new microprocessor every six months. > ..... > Rune --------------------- I sympathize with what you were faced with, Rune. I spent several months writing a software package in assembly language for the 8086 back in the early eighties, creating routines and standard functions for carrying out operations in the format of the then brand new IEEE 754 floating point numbers. I had to learn to deal with each of Intel's eight special purpose registers and hated every moment of it. Roger Stafford
From: Rune Allnor on 14 Sep 2006 18:17 Roger Stafford skrev: > In article <1158259215.915274.233250(a)m73g2000cwd.googlegroups.com>, "Rune > Allnor" <allnor(a)tele.ntnu.no> wrote: > > ..... > > Well, this is one of many "pet peevees"(?). My first professional > > degree (BSc) was as a computer engineer. The first three semesters > > were spent learning the 8086 virtually on the shift regisetr level. > > The next two were spent learning the 286. Then the 386 was > > released and I decided that I had better ways of spending my > > time that learning a new microprocessor every six months. > > ..... > > Rune > --------------------- > I sympathize with what you were faced with, Rune. I spent several > months writing a software package in assembly language for the 8086 back > in the early eighties, creating routines and standard functions for > carrying out operations in the format of the then brand new IEEE 754 > floating point numbers. I had to learn to deal with each of Intel's eight > special purpose registers and hated every moment of it. The issue that REALLY killed my interest in CS was the MSDOS memory mapping madness. In -90 I spent the equivalent of $3000 on a once-in-a-lifetime offer: 386 processor (prep'ed for the 387, which I installed a year later), 40 MB hard disk and a whopping 2 MB RAM. Yeah. Truly a once-in-a-lifetime offer, all right... Anyway, at the time I knew my way reasonably well around x86 assembler code. But there was no way I was able to get out of that 64 kbyte page size inherent in the MSDOS memory schema; let alone get access to that elusive extra 1 MB of RAM I had paid deer $$ for. When I realized that actually getting access to the available HW resources would require some 90% of the coding effort in any realistic project, I started looking for other things to do. Oh well. Rune
From: Steve Amphlett on 14 Sep 2006 18:34
Rune Allnor wrote: > > The issue that REALLY killed my interest in CS was the MSDOS > memory mapping madness. In -90 I spent the equivalent of $3000 on > a once-in-a-lifetime offer: 386 processor (prep'ed for the 387, > which > I installed a year later), 40 MB hard disk and a whopping 2 MB RAM. > > Yeah. Truly a once-in-a-lifetime offer, all right... > > Anyway, at the time I knew my way reasonably well around > x86 assembler code. But there was no way I was able to get > out of that 64 kbyte page size inherent in the MSDOS memory > schema; let alone get access to that elusive extra 1 MB of RAM > I had paid deer $$ for. When I realized that actually getting > access to the available HW resources would require some 90% > of the coding effort in any realistic project, I started looking > for other things to do. Ok, my second big assembler/machine code project was using an Acorn ARM chip (~1988-1989). That was true 32-bit , woooo! An interest reawakened. Mind you, x86/x86_64/EM64T/IA64/etc these days, who cares? I wonder who actually writes assembler for these chips and how long their skills are useable. |