Rustify it? #205
Replies: 3 comments 4 replies
|
@aka1prime-svg can you explain which parts would be improved if rewriten in rust? the app takes 1% cpu on idle and the ui react within 16ms it already uses rust for the backend and rust is just not the right tool for making interfaces also you mentioned it has bugs, which ones? |
|
They wrote zed in rust. It works pretty well, Rust / C interpreting js/ts is inherently slow. it already uses rust for the backend and rust is just not the right tool for making interfaces -> maybe you are not faimiliar with industry standards and trying to get around with patch tools |
|
I just didn't write anything here because the discussion wasn't really relevant from an engineering point of view. First of all, I don't really understand what you're talking about. The cold start of the app is instant, the binary size is <10 MB, startup RAM usage is even lower than Warp's, despite Warp being fully native (Rust), CPU idle usage is 0%, the interface is very simple (and React/TypeScript is perfectly fine for this), everything is optimized and virtualized, etc. And most importantly, the core components: backend, PTY, OS/FS integration, git, etc. are already written in Rust, while the renderer is WebGL. If a repo contains 80% TypeScript, that means absolutely nothing by itself. You can have a pure C/C++/Rust app that feels laggy, has memory leaks, and so on. Zed uses its own GPUI library, which isn't even stable for production yet, as it's primarily tailored to Zed itself. And here, GPUI would only be used for the interface, not for terminal rendering. I could say a lot more from a technical perspective about why this discussion simply isn't relevant, but I guess that's enough. |
Uh oh!
There was an error while loading. Please reload this page.
Initial prototype is quiete good, but its far from real world usability!
The fact that js is involved makes it buggy & slow!!!
Look at real world terminals like alacritty & tilix...
Any thoughts on making it useful with rust?
All reactions