This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Huh ??? Afrer reading soooo amny great things about IDEA I decided to go for it. Working curently with textpad and WSAD. So perfectly good code I take and make a project. Paste code and get zilion errors. Click compile and it still compile. If there is error it is not supose to compile right. :roll: I mean ..... 20 times cheaper textpad does better job. I tried it pised off with memmory eating WSAD... Im not complaining any more im good boy... WSAD is great ... textpad is great ... memmory is cheap ... ahhh nirvana again [ July 12, 2004: Message edited by: Gregg Bolinger ]
If your only complaint with IDEA is that it initially behaved in a way you didn't understand which was confusing, I suggest you hold off judgement temporarily. I can assure you that it can and does successfully compile code for thousands of develoeprs every day, and while it's possible to get incorrect code errors if you do the right sequence of things in certain builds (I've had this happen twice since I started using IDEA last year, and both times clearing out the caches made everything fine) such bugs are certainly not an everyday occurence.
I can't comment on your specific scenario with the information provided, although if you added a lot of files and didn't keep the IDE open very long it may not have finished indexing. There's a square indicator at the top right of the file you're currently editing which is colored to indicate the presence or absence of errors and which is blank while indexing is still in progress. (Note that IDEA stops parsing if you focus on a different application since Windows isn't very good at allocating processor resources). It's possible to compile successfully before indexing finishes because compiling is a much simpler process. This might be the explanation for the behavior you encountered.
Some people have found that IDEA takes an unnecessarily long time to parse very large files, so if you're working with files which are multiple thousands of lines long you may want to pass on IDEA for now (optimizing performance and memory usage are going to be major focuses of the 5.0 release which will probably address that issue).
I tried it pised off with memmory eating WSAD...
IDEA, for the record, is not all the memory friendly itself. Usually when I'm working the memory usage floats anywhere between 80 megs and 220 megs. And my projects are not particularly big or complex by industry standards.
Joined: Oct 26, 2003
80 megs and 220 megs is great WSAD eats 2-3 times (of 220).
well I am sure it works for you. Well many people don't realy have time to play with IDE. I need need something for fast coding/debuging(sometimes). IDEA even complains about my comments lol (well I hope my previous instructors will not read this). I really dont care if coments are writen right (and I am sure it can be turned on and off). I will keep wsad and textpad for now.
TextPad is wonderful for simple programs. I've used it for years. IDEA is good for larger projects. I like it a lot. Learning it is faster if someone who has already used it can show you how to use it. What if you try just a simple class first and then tackle a larger project.
JavaBeginnersFaq "Yesterday is history, tomorrow is a mystery, and today is a gift; that's why they call it the present." Eleanor Roosevelt
IDEA is good with a huge collection of features. but there are some drawback its consume more memory than eclipse. you should wait half of your time for its updating process every time you add a new library , change target jdk , change some code (it has not incremental building and if so i didnt find yet) ,...
WSAD is good for large enterprise scale projects that involves many EJBs , web applications ,etc
I'm saying this in the nicest and helpful way I can think of. If an IDE/Editor that is highly favored among professionals in the industry is complaining that much about your code and comments, I would highly recommend looking into why that is. Learning good programming habits early on is vital. Bad habits are really hard to kick.