Basically the IDE one needs to take into account that your program is broken all the time, yet you want code completion for everything else that is actually correct.
Also it needs to respond immediately after asking for completion, as anything beyond 2s is frustrating development experience.
You also want to get real time errors and warnings, just for the parts that are actually broken, not a wall of text like many batch compilers that fail to understand the remaining of the file.
Also you want to be able to do code refactorings, regardless of the compilation state.
So basically you want a Smalltalk/Lisp Machines like experience.
Also it needs to respond immediately after asking for completion, as anything beyond 2s is frustrating development experience.
You also want to get real time errors and warnings, just for the parts that are actually broken, not a wall of text like many batch compilers that fail to understand the remaining of the file.
Also you want to be able to do code refactorings, regardless of the compilation state.
So basically you want a Smalltalk/Lisp Machines like experience.
Anders has a nice interview about this,
https://channel9.msdn.com/Blogs/Seth-Juarez/Anders-Hejlsberg...