3 ms·
My experience on Windows 11 wasn't as bad as yours, but I opened a small Rust project with Lapce (~20 files) and it uses 1400MB of RAM vs VS Code's 900MB, and h
by roarcher 3y ago
My experience on Windows 11 wasn't as bad as yours, but I opened a small Rust project with Lapce (~20 files) and it uses 1400MB of RAM vs VS Code's 900MB, and has very noticeable latency when navigating the code and typing.
But like you said, it's pre-alpha, and I hope this project succeeds. I'm sure these issues are solvable. It's exciting to see Rust-based non-web UI libraries finally starting to become usable for reasonably complex apps.
- panekj 3y agoLapce cannot use that much of memory, it's most likely that Rust Analyzer has allocated majority of it.
- roarcher 3y agoMy VS Code instance is also using Rust Analyzer. Edit: I just disabled RA in both editors and restarted them. VSCode is now at 320MB and Lapce is at 770MB. Edit 2: To be clear, my above comments are meant in the spirit of an informal bug report/feedback. I get that Lapce is a labor of love for its core developers, and I'm not shitting on it. In fact I think it's pretty impressive. I'm keeping an eye on it as something to potentially switch to once it matures a bit.