On Mon, Feb 22, 2010 at 10:38 AM, John Chung wrote: > It is not the Java (writes everything) but the reliability!!!!! NetBean sinks.... > How bad it is? Is it standard NetBean from Sun or some modified version? I do not have experiences with NetBean. But for Eclipse, it seems to be much better over the years. I tried to use Google's Android IDE and it is not bad (my youngest brother wrote an Android Application and I was trying it on the emulator -- I am not into smartphone myself even though I used to be a PDA fan). But for vendors IDE based on Eclipse, it can be bad since they need to write plugins to interface with the vendor toolchain and their hardware/software components (simulator, programming and debugging tools, etc). That can drag the whole thing down. I tried to use Eclipse with OpenOCD for ARM testing, so far I like IAR EWARM with J-Link far better than Eclipse/GCC/OpenOCD (with J-Link or FTDI based debugger). The hardware debugging plugin is still tricky to setup even though Eclipse works nicely with GCC-ARM. It is said that using NetBeans with AVR is as easy as 1-2-3. ;-) http://www.ethernut.de/nutwiki/Developing_for_AVR_with_NetBeans%3F_Easy_as_1-2-3! Let's see how Microchip can do with PICs. ;-) -- Xiaofan http://mcuee.blogspot.com -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist