Should I even mention the God-awful debugging? Ugh.Īs for intellij, the only real use it gave me was making me hate my mouse.
Java cares so little about the developer experience that I don't think they even take it into consideration, unlike Go or Rust. Yet at least half of the time when working with these project it's wrestling with esoteric configurations. The whole point of java was to make large, dependable, and easily refactorable projects that were also highly portable.
#KARABINER ELEMENTS APPLE SILICON DOWNLOAD#
You might be able to download the repo and open it, but be prepared to get reamed for a week trying to get intellij, maven/gradle, and all the other dependencies to talk to one another. I've worked on many jvm projects not long ago, I've never had one that would work just out of the box. Yeah, all of this is no longer true for java.
#KARABINER ELEMENTS APPLE SILICON CODE#
Rust support and JetBrains' slow progress on many issues, I will probably switch to VS Code at some point. But with the progress that Visual Studio Code makes with e.g. I have a ToolBox subscription (among other reasons because IntelliJ is still the best Java IDE).
There are some issues about this in their bug tracker, but the JetBrains personnel either do not seem to understand how the Linux graphics stack works (and come with non-solutions) or say that it is low on their priority list. My only gripe is that they do not have native Wayland support and as a result the IDEs are blurry with GNOME fractional scaling. The JetBrains IDEs are lightning-fast, including indexing. I never had that issue on Linux with a Ryzen CPU (3700X) though. I have noticed the same issue with my Intel MacBooks, it's slow and the fans spin loudly. These must be macOS issues or problems with the limited thermal envelopes ofIntel Macs. This release makes the IDE so incredibly fast! Indexing dependencies happens magnitudes faster than Intel version. That joy has subsided in recent years with performance on Mac Intel.
0 kommentar(er)
