5 ms·
I really hope it's not Electron-based.
by torginus 5y ago
I really hope it's not Electron-based.
- he_is_legend 5y agoUnlikely. The rest of their programmers toolset are mostly java based.
- f311a 5y agoGoogle translate from a dev vacancy: 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.
- ac130kz 5y agoNow that's interesting, let's hope it's not immediate mode based and is closer to SolidJS (without Virtual DOM) than modern React, which clearly has no long-term future.
- ac130kz 5y agoI really hope it's not Java mess either: no Wayland support, lags
- ff23ff23333 5y agoYes, I also hate Java so much!
- pb82 5y agoReally? I'm using their IDEs on Fedora 35 with Wayland. Seems to be working fine.
- ac130kz 5y agoNow disable XWayland and try again
- mariusmg 5y agoNo chance of that, everything they do is in Java...
- xyproto 5y agoTo be fair, Wayland is still new (compared to how long Java has existed), and Java/OpenJDK may improve support in the future.
- ac130kz 5y agoWayland is almost 15 years old by now, and it's on track to be enabled by default on most distros as well.
- bscphil 5y agoSame. Similarly, since VS Code is the obvious comparison here, I really hope they're planning to open source the basic version of this once it's out of beta. I could really see myself using this if it manages to be both open source and actually lightweight and not a 300+ MB blob.
- arnvald 5y agoApparently it's not: https://twitter.com/himanshub16/status/1465238053979447296 https://twitter.com/himanshub16/status/1465238053979447296 In the thread someone from JB mentions it's mostly JVM + some Rust
- robm50 5y ago(the tweet: https://twitter.com/hhariri/status/1465239810050830338?s=20 https://twitter.com/hhariri/status/1465239810050830338?s=20)
- mikkelam 5y agoThe UI is probably written with compose https://github.com/JetBrains/compose-jb https://github.com/JetBrains/compose-jb
- asattarmd 5y agoI believe so as well. Compose is very similar to Electron. Jetbrains Toolbox (which uses compose) uses 500mb memory which is on par with what Electron would use for such a simple app.
- torginus 5y agoI really hope that's not the case - at least the browser has an excuse of being a scripting platform, a 3D and 2D rendering and layout engine, a video streaming platform, a database, a server and who knows what rolled into one - that Toolbox thing hopefully has less than 5% of that in its codebase.
- wiseowise 5y agoExcept Electron is 8 years old, and Compose desktop has started active development half a year ago.
- iruoy 5y agoI just checked. On my Windows laptop from work it uses 18.5 MB in the background. It uses 220-240 MB in the foreground though. Which seems totally unnecessary. 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.
- kaba0 5y agoWhy would it be similar? It doesn’t need all the unnecessary abstraction of a browser/DOM. Also, initial memory usage doesn’t mean it scales the same way from then on.
- 5y ago
- zRedShift 5y agoOfficial response: https://blog.jetbrains.com/blog/2021/11/29/welcome-to-fleet/#remark42__comment-ac6e4928-dd81-4d93-895a-ece157a8e7f4 https://blog.jetbrains.com/blog/2021/11/29/welcome-to-fleet/... 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 :)