This project is being built with heavy use of LLMs. LLMs are used as a tool, not as a brain replacement.

I do consider the code to be my, and I am spending a lot of time caring about the code quality. So I consider it to be rather readable and maintainable. It might not be the idiomatic example of compiler-adjacent tooling (I don't have that much domain experience), but I am working on improving it as I work on it.

So if it is slop, then it is my slop, and the best way to help is to tell me what's wrong. This way I will be able to learn something and hopefully make the project better.

I don't know what to think about it.

[–] ddroid@fosstodon.org 5 points 2 days ago

@fargeol @codeinabox Haha same, but I guess they're atleast trying to care about code quality.

But hey, let me know your thoughts.

[–] BB_C@programming.dev 5 points 2 days ago

Regarding the rust-glancer announcement itself, I hope the author is aware that lspmux (formerly ra-multiplex) exists, and zram. If lspmux didn't exist, then yes, editor restarts would have been annoying, but that has been a solved problem for a few years already.

Also, I'm not sure hitting SSD storage too much is good strategy in general, but maybe that's an overstated concern.

Otherwise, yes, RA could do better in memory consumption and some other aspects. And yes, the LSP protocol itself is not ideal.

In any case, introducing new ideas and approaches is always good, especially when there is no "fragmentation" concerns, which I think is the case here.

[–] Sibbo@sopuli.xyz 3 points 2 days ago

Thanks for sharing, that's an interesting read!