Unix/Java devs usually have prefered to survive without IDEs but thatís the
one reason I dumped Java as my prefered language altogather few years back.
I guess it's good to be without IDEs when you are still learning the language,
but once you have mastered it, you want to concentrate on application logic
rather then playing around with command line switches and jotting down error
line numbers. The reasoning stated in the article stands on rather weak grounds.
Lets see... #1. Eliminate IDE dependence! Every thing that's going increase
dev productivity is ALSO going to create itís own dependency on it. Isn't
it? Should I walk to my office instead of driving down because my speed advantage
has became dependent on my car? #2. Lower cost! Good commercial IDE doesn't
cost more then a week pay of typical professional programmer. Unless Iím
fresh out of school without any money in my pocket and spending all my days
developing freeware programs, the money you would have saved wonít even pay
for apartment rent. #3 system resourcesÖ Go get out and get 1 GHz 256MB machine
for under $800! Thatís not reason to write my programs in Notepad!!

Lastly, just in case Unix devs have forgot to catch up, IDE has evolved far
beyond a one-key-compilation facility. You put break points, look at variable
values in watch, execute few lines while still in run mode, drag and drop
other people's components, database fields to quickly present a demo, visually
design the user interface instead of playing with pixel values and layouts...
Look at MS .Net IDE and you may know where the world stands right now...
It's all about eveolution. Things doesn't work all the time but that's why
they change and gets better. If you stay behind at where we started, you
don't evolve.


I used to have an open mind but my brains kept falling out.