embedded systems industry applications

Do your own homework.

Ian

You missed some.

OK, you missed a lot. Probably more than half of the embedded market, in terms of numbers.

Into which category goes the automotive engine computer?

A home thermostat?

Traffic signal control?

Metal stamping machine?

Etc. etc. etc. When someone tells you computers are everywhere, they're not kidding. We're so used to them that we don't tend to think of them as computers, but they're there, and they need to be designed in by someone.

I agree you said that computers are everywhere, and looks like embedded systems field is getting bigger and tend to be different from traditional embedded systems. Compared with other industries, do you think embedded systems field is a large field? Now, most hot jobs in the market are Java and .NET, and they are not used in embedded systems at all. I think embedded systems developers really need to understand computer systems well, not just programming itself.

What do you th> > >Real Time/Embedded systems is a large industry, and there are many

What you are asking is not easy to answer. Embedded is a fairly broad term these days. It can be a simple 4bit micro in a thermostat to a full blown PC controlling a machine. It is a large field as just about everything you use has some sort of computer embedded into it. Even your PC has some embedded firmware on the motherboard.

AS for .net/java, choose you language for the job at hand. Those who say that c++ is crap or java is rubbish clearly have no idea what they are talking about. Each language has its benifits and pitfalls. I have read so many people ranting about why one language is better than another and it is all bullshit. I am not going to use java in my 4bit thermostat that only requires a few dozen lines of assembler. Likewise i am not going to use assembler to write a full graphical interface where languages like c# will do it for me in a fraction of the time.

IF you ask me, I think embedded firmware should be a discipline by itself. It is my honest opion that hardware engineers should stick to hardware and computer engineers stick to software. Neither seem to cross well into the firmware space.