"I crashed my PC when I simulated my code with Keil debugger, so what?"

While I haven't crashed my PC with any 8052 tools yet, I've crashed my PC with just about everything else. Microsoft development tools, Word, Adobe, MP3 players, Netscape, Mozilla, and Internet Explorer. They've all crashed my PC at some time. While certainly not excusing errors in applications, it seems to me the common denominator is Windows. This is why I've started making an effort to move to Linux--in fact, I do almost everything under Linux now except email (I like Eudora which isn't available on Linux).

There is nothing wrong with a command line interface. If that's what you're comfortable with, go for it. I still do all my file management in a DOS window. I can almost always copy files faster by opening a DOS window and running the appropriate COPY command than copy/pasting files from one directory to another.

When it comes to 8052 development, I used to go with CLI but have since moved using IDEs. Of course, you have to be happy with the editor. But a nice IDE can give you an editor, simulator, and the compiler/linker all in a single program--often with integrated links to full-blown ICE/emulators.

*IF* the IDE is well-designed, it can be much easier than learning command-line parameters, linker file settings, etc. On the other hand, if the IDE is not well-designed then you end up spending time fighting to get the IDE to do what you could have configured manually with command-line options and linker settings in a flash (once you read the manual).

I think "well-designed" should mean intuitive. I shouldn't need to read the manual to assemble/compile a simple program. Sure, if I want to use fancy features than I'll need to investigate. But if it takes me more than about 10 seconds in the menus to figure out how to assemble a 2-line assembly program, the IDE needs work.

That's my opinion anyway.

Regards,
Craig Steiner