REVIEWS / DEVELOPER TOOLS / OWNER INSIGHTS

🦉 WE READ 76 OWNER COMMENTS

JetBrains IntelliJ IDEA Ultimate: what owners actually say

Owners universally praise the core IDE quality but are increasingly frustrated by JetBrains' fragmented one-IDE-per-language strategy and plugin feature parity gaps

YOUTUBE · 42 HACKERNEWS · 15 REDDIT · 10 STACKEXCHANGE · 9

What owners complain about

  • Product fragmentation COMMON

    Multiple users express deep frustration that JetBrains splits functionality across many separate IDEs (IntelliJ, PyCharm, DataGrip, CLion, etc.) instead of offering a single unified IDE. Users who work in multiple languages find the one-IDE-per-language model painful and want a single product with language plugins.

  • Plugin feature parity gaps SOME

    Owners report that IntelliJ Ultimate with language plugins (e.g., Python) is missing features compared to the standalone IDEs like PyCharm. Specific complaints include debugging restrictions and differing UIs between products.

  • Settings don't sync across IDEs SOME

    A user reports having to manually export/import trivial settings like font size every time they switch between JetBrains IDEs, spending 15 minutes on what should be automatic.

  • Performance and memory issues SOME

    Users report increasing hanging and glitching over the past year. Memory consumption is notable — one user casually accepts 3GB RAM usage. Apple Silicon users found performance issues traced to running Intel-optimized Java rather than ARM-native builds, requiring manual runtime swaps.

  • Real-time compilation inferior to Eclipse FEW

    A former Eclipse user notes IntelliJ's real-time error detection is slower and less reliable than Eclipse's, and enabling the feature makes the IDE sluggish.

What owners love

  • Best-in-class for Java development

    Multiple owners call IntelliJ a 'no-brainer' for Java work, with one calling it 'a piece of art.' Long-time developers with 10+ years of experience across vim, Emacs, and VS Code still consider it the top choice.

  • Exceptional refactoring and code intelligence

    Owners praise project-wide refactoring as reliable and instant — one user directly contrasts IDE-native refactoring (rename a method across the whole project with a keystroke) favorably against LLM-based approaches that go file-by-file and produce unreliable results.

  • Depth of features

    Users love the sheer breadth of capabilities — 'so many features, you couldn't possibly know them all but I love that they're there.' Specific features like language injection are highlighted as time-savers that users didn't even know existed.

  • Worth the subscription cost

    Multiple owners consider their IntelliJ subscription some of the best money they spend annually, with strong loyalty — one says they 'cannot switch back' to Eclipse after using IntelliJ.

  • Unified platform architecture

    Owners appreciate that all JetBrains products are built on the open-source IntelliJ Platform, meaning core improvements automatically benefit every IDE in the lineup.

Surprising patterns

  • Several users prefer IDE-native code intelligence (indexing, LSP, structural refactoring) over AI/LLM-based coding tools, explicitly choosing deterministic refactoring over 'LLM hallucinations.'
  • JetBrains created Kotlin specifically to solve their own internal Java code complexity and null pointer exception problems — the language was born from dogfooding their own IDE development.
  • Apple Silicon users discovered IntelliJ performance issues were caused by running Intel-optimized Java builds, and manually swapping to OpenJDK or Azul JDK with adjusted Xmx settings dramatically improved smoothness.

WHO SHOULD SKIP IT

Polyglot developers who frequently switch between languages may find the fragmented multi-IDE model and plugin feature parity gaps frustrating enough to prefer a single-editor solution like VS Code or a configured vim/Emacs setup.

7.4/10 GYIBB verdict
Full review →

Synthesised from 76 real owner comments across 4 platforms. Every point is grounded in the comments — no marketing, no AI guessing. How we do it →