21–30 of 77 posts
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?
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 :).
The problem is that Intellij is written in Java, using the hotspot JVM, which is JIT compiled. 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…
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.
> It is a memory hog 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 ar…
Just to be specific: Is this your experience just running the IDE at default settings, or did you increase the JVM heap size for it and had no effect? If you run it at default settings, the memory footprint will stay My experience on this is that it's a great idea to bump the memory size to 4GB. I have not done any benchmarks on it, but it feels much faster in regular use.
Earlier quoted context omitted.
Does Doom Emacs provide the same functionality as IntelliJ IDEA?
Some additional anecdata: on my maxed out 16” (admittedly Intel) Mac, IntelliJ/PyCharm/Goland/Webstorm are all quicker to start than Spacemacs. I haven’t tried Doom Emacs but don’t get the impression it would be much quicker.
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 :).
The problem is that Intellij is written in Java, using the hotspot JVM, which is JIT compiled. 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…
So it is apples vs oranges. One is faster here the other there.
GC might be an issue, but for me IDEA feels fast and the added benefit of code navigation vs e.g. vim is worth it.
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 :).
There isn’t a clear order for feature introduction after stuff hits IntelliJ.
However, they mentioned a few times that people who need multiple tools often pick individual apps simply because they are much lighter weight than IntelliJ.
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.
Why? It's meant for pair programming and has already been done as "Live Share" in Visual Studio / Visual Studio Code. It's a way to work together in only what you give the guest access to.
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.
Hopefully they will support Wayland in next version.
- Some graphical intensive parts (such as the markdown preview renderer) cause crashes. Turning preview off remedies this.
- HiDPI situation is garbage as usual (but that's a Linux thing in general). IntelliJ renders at half resolution so it's not as crisp as it can be, but it's perfectly usable.
- The 'everything is a window' design choice, combined with the 'you cannot click on any IntelliJ instance if _one_ of them has a window open' is worse on Wayland. This may be due to my WM of choice (Sway), but there are often prompts that are rendered behind popup windows.
- context menus have issues with immediately closing due to some mouse event. I now use keyboard shortcuts instead of mouse clicks as a workaround. As a bonus I am now discovering all sorts of shortkeys that boost my productivity.
- overall rendering performance (like input lag or scrolling FPS) seems to be worse on Wayland compared to X11, but I have not benchmarked this. May just be me being a bit too demanding/expecting from the Wayland performance promise.