search

oxalica / nil

NIx Language server, an incremental analysis assistant for writing in Nix.
Apache License 2.0
1.4k stars 43 forks source link

Comparison with `rnix-lsp` #31

Closed hab25 closed 2 years ago

hab25 commented 2 years ago

Or at least describe what motivated the creation of nil, since comparisons are hard to keep up-to-date when both projects are under active development.

This should help users choose which one to use.

The discourse announcement has no mention of rnix either, but when reading

aiming at better coding assistance

one often wonders: better in what way(s)?

Kranzes commented 2 years ago

comparison: nil is better

i-am-logger commented 2 years ago

Unfortunately the contributor of rnix-lsp died via the repository readme comment

hab25 commented 2 years ago

Unfortunately the contributor of rnix-lsp died via the repository readme comment

Right, but others have commit access, and forking is, of course, possible

oxalica commented 2 years ago

As mentioned in README, there's a list of noticeable features in docs/features.md, if you want a comprehensive answer.

I used to playing with rnix-lsp for a short period of time, but it's more like a better-than-nothing basic tool and doesn't really improve my editing experience, plus some functions are simply incorrect (including the parser rnix, before I made some PRs). Its structure seems not scalable enough for more rich features (rust-analyzer for comparison), and it's not actively developing recently. Thus I try to recollect my ideas to make this project.

It's intentional to NOT put point-to-point comparison with other LSPs. It would be rather judged by you users.

hab25 commented 2 years ago

It's intentional to NOT put point-to-point comparison with other LSPs. It would be rather judged by you users.

@oxalica that's reasonable. I identified what you just shared as being largely anectodal (so I understand not wanting to call it "documentation"), but even so it does help me know what to look for when judging the pros/cons of both projects.

Maybe just having this issue exist is enough; people can find it with their search engines.

You can close if you want.

hab25 commented 2 years ago

Correction here:

I identified what you just shared as being largely anectodal

The feature list is comprehensive and not anecdotal.