OpenIDEA: Rust-based IntelliJ IDEA clone launches on GitHub
New IDE mimics JetBrains' interface with Rust backend, but Hacker News questions whether it's truly Rust and if benchmarks are fair.
What to know
- OpenIDEA claims to replicate IntelliJ IDEA's interface and workflow in a native Rust-based app, but its actual composition is 60% TypeScript frontend and only Rust glue code, drawing criticism over misleading framing.
- Performance benchmarks comparing OpenIDEA to IntelliJ IDEA lack feature parity, making claims about memory and speed reductions questionable.
- IntelliJ IDEA Community Edition has been free and open-source since 2009, raising questions about the necessity and value of a from-scratch rebuild.
The dispute Whether OpenIDEA represents a genuine technical innovation or is primarily a repackaging of existing components (Tauri, TypeScript, LSP) marketed with exaggerated Rust credentials. · positions read across 12 posts and comments
The 'rebuilt in Rust' claim is misleading; most implementation is TypeScript with only Tauri glue code in Rust.
-
“It seems it uses CodeMirror [1] in the Tauri frontend (60% of total code is typescript), but uses rust in the backend (30%).”
exceptione · Hacker News ↗
Performance benchmarks are unfair because they don't account for feature parity between OpenIDEA and IntelliJ IDEA.
-
“In the benchmark[1] the cpu, memory and quit time (!) are compared, but does it makes any sense without feature parity?”
atrokhymchuk · Hacker News ↗
A rebuild is unnecessary because IntelliJ IDEA Community Edition is already free and open-source.
-
“why do we even need the rebuilt? idea is already opensource[0].”
atrokhymchuk · Hacker News ↗
l0ng-ai OpenIDEA project creatorJetBrains IntelliJ IDEA publisher
How it unfolded 4 developments, newest first · click a bar or a number to jump articlespostscomments
-
4
Debate intensifies over misleading 'rebuilt in Rust' framing
A commenter argues the 'rebuilt in Rust' claim is misleading: code processing uses standalone LSP processes, the frontend is WebView with TypeScript, and only the Tauri glue code is Rust. They also express skepticism about memory usage claims.
“Calling it "OpenIDEA" is a bit misleading...saying that it was rebuilt in Rust is at least as much misleading: the code processing is still standalone LSP processes, frontend is WebView with typescript, only Tauri glue code is Rust.”
— avallach -
Correction: Rust is more than just Tauri glue code (https://github.com/l0ng-ai/openidea/issues/568#issuecomment-...). But considering that in an IDE the two performance critical parts are code processing (LSP) and frontend, I wonder how much benefit can you really get by making everything except of them in Rust.Overall I actually agree that VSCode…
2 more of the top 3 · 5 posts in this stretch
-
Calling it "OpenIDEA" is a bit misleading. IntellijIDEA is free and open source (Apache 2.0) since 2009. Paid subscription basically gives you extra plugins. And as others pointed out, saying that it was rebuilt in Rust is at least as much misleading: the code processing is still standalone LSP processes, frontend is WebView with typescript, only…
-
10 years ago and earlier it was cool IDE.What are they doing now? crisis of ideas and just hyping? pity.
-
-
3
Critics question need for rebuild when IntelliJ is already open-source
Commenters point out IntelliJ IDEA Community Edition has been free and open-source since 2009, and raise concerns that performance benchmarks lack feature parity.
“why do we even need the rebuilt? idea is already opensource[0]. In the benchmark[1] the cpu, memory and quit time (!) are compared, but does it makes any sense without feature parity?”
— atrokhymchuk -
why do we even need the rebuilt? idea is already opensource[0].In the benchmark[1] the cpu, memory and quit time (!) are compared, but does it makes any sense without feature parity?[0]:
1 more of the top 2 · 2 posts in this stretch
-
Uses Typescript for the most part, not much better than Electron stuff, cannot use the InteliJ plugins powered by the JVM, it is vibe coded, no thanks.
-
-
2
Developers question actual Rust composition and architecture
HN commenters examine the codebase and note the project uses CodeMirror in a Tauri frontend (60% TypeScript), Rust in backend (30%), and LSP processes. The claimed memory reduction is questioned given the WebView overhead.
“It seems it uses CodeMirror [1] in the Tauri frontend (60% of total code is typescript), but uses rust in the backend (30%).”
— exceptione -
Interesting project. It seems it uses CodeMirror [1] in the Tauri frontend (60% of total code is typescript), but uses rust in the backend (30%). Surprising to see that Tauri is apparently good enough for the three platforms it needs to support (or it uses a lot of hacks, I don't know). The advertised memory reduction is remarkable as I expected a…
2 more of the top 3 · 4 posts in this stretch
-
2025 was all about 'Rust' on HN and 2026 is all about 'rebuilding everything in Rust'. Comical on one level and yet intriguing.
-
From the promo video:> completion from language serversThat's exactly the thing that I like about idea: It's better than that.
-
-
1
OpenIDEA project launches on GitHub
OpenIDEA, an IDE claiming to rebuild the IntelliJ IDEA experience in Rust, appears on GitHub. The project offers IntelliJ IDEA-style keymaps, tool windows, search-everywhere, editor, code insight, debugger, Git, terminal, database and HTTP clients for 60+ languages across macOS, Windows, and Linux.
“OpenIDEA brings the IntelliJ IDEA way of working — its keymap, its tool windows, its search-everything habits — to a native app with a Rust core.”
— OpenIDEA project description · source -
first by HN Frontpage, 10d ago
-
So that I understand...I guess the logic here is: If I love this project, I should renew my JetBrains subscription...so that they can keep having money to fix bugs in their IDE...so that you can keep reverse engineering it?Am I seeing this right?
-
What people are saying 2 voices from 1 site · best of 12 · verbatim
- Nov 1
-
This is fantastic. The Jetbrains Java fetish has always crippled these otherwise good tools.
-
The comparisons of speed and memory usage only make sense if there's feature parity.