I really hope it's not Electron-based.
It’s written in Kotlin mainly, a little bit of Rust for native parts, Skiko (Skija + AWT)
The UI framework is similar to Compose, but we started when Jetpack Compose wasn’t there :)
I wonder if they have plan to use Kotlin Native. But dogfooding is always good.
I hope they support wayland natively but its just not necessary atm.
The first distro to use Wayland by default was Hannah Montana Linux, 10 years ago. Only recently have more widespread distros started using Wayland by default.
Java is old, and Wayland is comparatively new.
In the thread someone from JB mentions it's mostly JVM + some Rust
You will be surprised, but we decided to create a new IDE from scratch and put together a bold team with a proven success track in creating tools inside JB. And right now we have a prototype and a bunch of bicycles.
Our program consists of several parts that communicate with each other over the network.
The first part is an editor that is written in a new cross-platform UI framework. When we made this framework, we were inspired by React.js and Swift UI.
The second part is a small program written in Rust that tells about the arrangement of files on disk and starts processes. File watcher, process monitor and HTTP client in one binary.
The third part is a server that analyzes the source code of the project. It can be IntelliJ, ReSharper, or LSP server.
This architecture adds flexibility: if you run all the parts on one computer, you get a classic IDE. And if on different machines, it will be convenient to work in the cloud or in a container.
Curious, why do you think that?
I already ditched the Toolbox app on macOS, because it marks the binaries as Intel only (while they're universal). The IDE's built in updater seems fine if you're only using the stable versions. So I think I'm just going to remove the Toolbox app from all my machines.