[Mike Betts]

Continued...

I was going to let my last post stand but this is still sticking in my craw...

First, you are comparing a desktop software package which sells several millions of copies (hence revenues) against an embedded processor software package which sells several thousands (they make their profit in chip sales).

Add to that the fact that Mr. Gates and company make a product which is no longer ANSI compatible (therefore code is not portable).

An embedded processor software package is targeted at degreed engineers who program for a living. An embedded program is usually very small and compact, no megabytes wasted in useless hooks to windows... The embedded programmer's task is to make his code as small and efficient as possible.

The smaller and more efficient the code, the less chance of bugs to begin with. We usually don't need (or want) a lot of fluff...

The design cycle is usually to build a prototype development platform which accepts ICE and also has extra debugging aids added by the engineer. You only build a couple of these. After you have developed your code and debugged your hardware interfaces, you then redesign for a bare bones production system. Debugging in the production system, if required, is usually done by oscilloscope, logic analyzer and (perhaps) by the single LED you left on the board...

Actually, I just exaggerated... We normally do put a diagnostic serial port on the board to aid in maintenance.

I have used a lot of embedded development systems and rate MPLAB as one of the best I have seen (especially for a target chip which costs $5 each).

If you want to work in large computer systems with object oriented code which fill volumes of notebooks (if you were to print it out), go and be at peace.

I, personally, don't want a Pentium with it's inevitable blue screen of death determining if the airbag in my truck is going to deploy or not... I'll take a nice, small uC (with nice, small expertly written code) any day.

'nuff said... Sorry about the rant.