Jarkko Sakkinen
jarkko
One thing where I would use #rustlang rewrite: vim/neovim clone. Helix/Amp etc. have the problem that they try to do something new.
Actually the best would be if @neovim would join the club of Firefox, Linux etc. and provide shenanigans for rewriting parts of it in Rust. I promise to contribute in this effort, if that ever happens (no time for working on the shenanigans unfortunately).
2
1
3
@jarkko @neovim This is always the issue. It's sexier to start new things than it is to make incremental progress on existing projects, but the latter has a much higher chance of wide adoption. Neovim is amazing—no one wants to give it up—but allowing the Rust toolchain to coexist with C would definitely increase the pool of future contributors to the codebase. But the Rust community is developing a rep for being pushy, so obviously some diplomacy is needed.
1
0
1
1
0
1
This is totally incorrect. It is a different beast. Is Eclipse vim "with some breaking changes"?
Sorry, now I think I've flushed all this out of my system :-) Apologies...
0
0
2
Neovim
neovim@hachyderm.io@jarkko https://github.com/neovim/neovim/issues/8669 previous discussion.
Tl;dr we are considering multiple possible future implementation languages. Rust safety guarantees doesn't always work that well when you need integration with the internals of existing C code and its data. Zig with its deep C support might also be an option.
On the other hand, we're very happy to make good use of modern libraries and tools written in rust, like tree-sitter :)
0
0
0