| ▲ | Rust Glancer: Rust LSP using 100x less RAM(rust-glancer.github.io) |
| 36 points by matklad 6 hours ago | 18 comments |
| https://matklad.github.io/2026/08/21/rust-glancer.html |
|
| ▲ | matklad 6 hours ago | parent | next [-] |
| To clarify, author is https://github.com/popzxc, not me! My thoughts are here: https://matklad.github.io/2026/08/21/rust-glancer.html |
| |
| ▲ | dang an hour ago | parent [-] | | Your thoughts are quite cool! but I thought featuring the project itself would make more sense for a frontpage thread, so I'm going to merge the comments (such as they are) from https://news.ycombinator.com/item?id=49392654 and add your link to the toptext above. Thanks for drawing attention to this topic! |
|
|
| ▲ | skavi an hour ago | parent | prev | next [-] |
| Waiting for RA to build up the full in memory data structure for a large workspace is so painful. Honestly, I'd just assumed that was the only way and didn't realize Rust Rover was different. Does anyone have experience using that? Any tradeoffs? |
|
| ▲ | 762236 2 hours ago | parent | prev [-] |
| Why don't people explain their acronyms? What is a Rust LSP? |
| |
| ▲ | xixixao 2 hours ago | parent | next [-] | | People communicate with regards to the audience they expect. This is why Rust (it’s a systems programming language) and LSP (the language server protocol invented by VS Code) are not explained in the article. I am hoping I don’t have to define the words I used, but if in doubt, Google or ChatGPT are your friends. | | |
| ▲ | 762236 2 hours ago | parent [-] | | It makes sense to always explain acronyms. I always do to avoid random people reaching out for more explanations | | |
| ▲ | sfdlkj3jk342a 39 minutes ago | parent [-] | | > It makes sense to always explain acronyms. It does up until a point. Would you say the same about "AI"? What about "LLM"? On HN (Hacker News), I expect that most would find a definition for AI or LLM to be redundant today. LSP is borderline in my opinion, especially when the context of Rust is already given. |
|
| |
| ▲ | Fnoord 41 minutes ago | parent | prev | next [-] | | A Rust https://en.wikipedia.org/wiki/Language_Server_Protocol | |
| ▲ | francislavoie 2 hours ago | parent | prev | next [-] | | Language Server Protocol, it's what your IDE (like VSCode or other) uses to do linting, syntax checking, and "go to reference" stuff. | |
| ▲ | IshKebab 2 hours ago | parent | prev [-] | | LSP is a well known term among programmers these days. | | |
| ▲ | 762236 an hour ago | parent [-] | | Not if an LLM writes your code. I get thousands of lines of high quality Rust per day without ever stepping into VScode. | | |
| ▲ | wtetzner 32 minutes ago | parent | next [-] | | Then why not just ask the LLM to explain what LSP stands for? | |
| ▲ | 0x457 22 minutes ago | parent | prev | next [-] | | Very little quality, let alone high-quality, code is written in VSCode. | |
| ▲ | nasso_dev an hour ago | parent | prev | next [-] | | what's an "LLM"? ;3 | |
| ▲ | polyaniline an hour ago | parent | prev [-] | | How do you know it's high quality? | | |
| ▲ | 762236 an hour ago | parent [-] | | I made myself an expert at Rust before I started using LLM's, and I review the code. | | |
| ▲ | verandaguy 41 minutes ago | parent | next [-] | | You made yourself an expert in Rust and have never heard of an LSP? This seems surprising to me given that Rust was one of the first languages to broadly advertise a toolchain and editor integrations which rely on the technology. | |
| ▲ | polyaniline 27 minutes ago | parent | prev [-] | | Props to you. I've been writing Rust for around 7 years now and I couldn't QA 1000s of lines per day. |
|
|
|
|
|
