From: Lothar Scholz Date: 2004-08-28T08:59:42+09:00 Subject: Re: performance comparison Hello Alexey, >> This has nothing to do with the IDE, only with the compiler/parser. AV> Decent Java IDE gives you accurate code completion, continuous parsing AV> and compile on save. I.e., most of the time instead of typing names, you AV> select them from a drop-down of all visible identifiers in the scope AV> (with most likely choices at the top of the list). I doubt that very much typos that make it into compiled code are wrong identifiers. And typos in identifiers normally don't get there way in a runnable program. code completion is 90% usefull for faster development (typing) but not for avoiding typos. AV> When you type AV> something, your typos get highlighted as soon as you type them, not AV> several minutes later when you compile and run unit tests. Correcting AV> them in this way doesn't break the flow at all - which is very pleasant. This the responsibility of the parser/compiler not the IDE (the IDE has no AI for this, it's just a few lines of code to do this). AV> 3. AV> As a frequent code reviewer I've probably seen thousands of Java bugs, AV> but very small proportion of them were typos. This is drastically AV> different from my experience with all other languages, including both AV> Ruby and C/C++. Thats why i'm trying to only use Eiffel. Still much better when it comes to avoid errors. For example overwritting methods by accident. -- Best regards, emailto: scholz at scriptolutions dot com Lothar Scholz http://www.ruby-ide.com CTO Scriptolutions Ruby, PHP, Python IDE 's