[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-26794 at 8/26/19 6:53 PM: ------------------------------------------------------------------- [~jgammonred612] thanks a lot for reporting this. Definitely worth investigating. I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker. It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are quite unresponsive displaying the call stack and slow to accept inputs. IntelliJ stays very responsive, you can fluently step over while the call stack is still being built. I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. Compare yourself (done with the preference "Show method result after a step operation" turned off, thus the difference is not that extreme any more): * Eclipse: https://youtu.be/MkebG9L5xBQ * IntelliJ: https://youtu.be/tykb_xdjJEg On the other hand, remote debugging - I think - isn't the dominant usecase. was (Author: adietish): [~jgammonred612] thanks a lot for reporting this. Definitely worth investigating. I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker. It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are quite unresponsive displaying the call stack and slow to accept inputs. IntelliJ stays very responsive, you can fluently step over while the call stack is still being built. I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. Compare yourself: * Eclipse: https://youtu.be/MkebG9L5xBQ * IntelliJ: https://youtu.be/tykb_xdjJEg On the other hand, remote debugging - I think - isn't the dominant usecase. -- This message was sent by Atlassian Jira (v7.12.1#712002)