Built from scratch, based on 20 years of experience developing IDEs. Fleet uses the IntelliJ code-processing engine, with a distributed IDE architecture and a reimagined UI.
Well, heavy or not, open or close, JB have one of the best IDE’s out there. Not for nothing have Netbeans and Eclipse fallen off the radar of developers, especially in the Java and related fields.
That’s true 😅 . I like the keybinding (vim) implementation and the layers (it’s more abstraction but it works). But I thinking to moved, again, to Doom. In some parts Spacemacs feels fragile.
I haven’t looked but I don’t think there’s that much custom code in Doom Emacs for example… it’s mostly something that sets sane defaults and glue over disjointed points… most of my slowdowns have come from different kinds of parsers etc and native-comp compiles all the packages which speeds up load / execution times.
Well, heavy or not, open or close, JB have one of the best IDE’s out there. Not for nothing have Netbeans and Eclipse fallen off the radar of developers, especially in the Java and related fields.
BTW I use Emacs (spacemacs) for Rust dev.
Fun fact: I moved from Spacemacs to Doom Emacs because of resource consumption 😉
That’s true 😅 . I like the keybinding (vim) implementation and the layers (it’s more abstraction but it works). But I thinking to moved, again, to Doom. In some parts Spacemacs feels fragile.
Yup, made the move too a couple years back. It’s honestly quite amazing how robust/hackable they have managed to keep Doom.
Have you tried running Doom on nativecomp-enabled Emacs? It’s even speedier =)
I think what slows Emacs distributions down the most is custom Elisp code. Do those parts benefit from native compilation at all?
I haven’t looked but I don’t think there’s that much custom code in Doom Emacs for example… it’s mostly something that sets sane defaults and glue over disjointed points… most of my slowdowns have come from different kinds of parsers etc and native-comp compiles all the packages which speeds up load / execution times.