11–20 of 77 posts
Anyone else who finds the idea of having someone poke around in your IDE creepy or a potential security issue, it's possible to disable the Code With Me plugin which is enabled by default.
Started off as very slow on a not-terribly large project > cache cleanup > does not even start without trashing the .idea folder anymore > still slooow. Command + space takes forever (=seconds) to show the context menu. IntelliJ feels like a proper IDE now :).
It works great if you give it enough memory. It is a memory hog but its the best IDE I've ever used.
Started off as very slow on a not-terribly large project > cache cleanup > does not even start without trashing the .idea folder anymore > still slooow. Command + space takes forever (=seconds) to show the context menu. IntelliJ feels like a proper IDE now :).
Earlier quoted context omitted.
Has always been fast for me and Idea has been the best java IDE around. What specs do you run and how large is your project?
As someone who switches between doom emacs and intellij: If you have to ask questions like, "What specs do you run and how large is your project?" it is slow.
Hopefully they will support Wayland in next version.
Started off as very slow on a not-terribly large project > cache cleanup > does not even start without trashing the .idea folder anymore > still slooow. Command + space takes forever (=seconds) to show the context menu. IntelliJ feels like a proper IDE now :).
But IDEs, especially fully featured IDEs, are a terrible type of workload for JIT compilation. They're full of branches, which can easily cause recompilations, and the breadth of features mean that there is never really a spot hot enough to stay compiled outside of the editor itself.
I really wish AOT compilation was taken more seriously in the JVM world. Yes, I know about graal native-image and the various embedded commercial JVMs, but those are niches. It would be great if I could just precompile using O3 level compilation for a whole app using a standard JVM, and not have to worry about the weird and hard-to-debug performance fluctuations that come with JITs.
Started off as very slow on a not-terribly large project > cache cleanup > does not even start without trashing the .idea folder anymore > still slooow. Command + space takes forever (=seconds) to show the context menu. IntelliJ feels like a proper IDE now :).
It works great if you give it enough memory. It is a memory hog but its the best IDE I've ever used.
This is different from my experience, when working on Java projects with a few thousand source files and about 1 million SLoC.
Eclipse - had some problems with the autocomplete being slow to open, IDE was overall unresponsive and used around 2 GB of RAM
NetBeans - the cache folder filled up weirdly quickly (though that was NetBeans 8.2 not the new Apache NetBeans), but the IDE worked fine with around 1.5 GB of RAM usage
JetBrains - project was slow to open (+while indexing), but the IDE performs okay with 0.5 - 1 GB of RAM usage (though more needed when running/debugging)
Of course, this would become more of an issue if you have something like 4 or 8 GB of RAM available.
Disclaimer: this is anecdotal data and i may be wrong in regards to latest versions of the IDEs, since i only use JetBrains products nowadays.
Earlier quoted context omitted.
It works great if you give it enough memory. It is a memory hog but its the best IDE I've ever used.
They really need to update the default memory footprint. The 750MB default isn't enough for any projects these days and they don't exactly make it obvious how to update it to 2-4GB.
Earlier quoted context omitted.
As someone who switches between doom emacs and intellij: If you have to ask questions like, "What specs do you run and how large is your project?" it is slow.
Does Doom Emacs provide the same functionality as IntelliJ IDEA?
The thing is, as far as I can tell, there's a very high overlap between the list of features I don't use, and the list of features that contribute to the sluggishness.