Rhai VS helix

The OS would be built in Rust and the module system could be made using ELF executibles (fast, but it could be really hard to implement modules to communicate with the kernel), WASM (can compile from many languages, slower but not too slow, APIs can be simple enough to implement if the correct VM is choses) or even a custom scripting language like rhai (slower, but best way for the implementation [way to connect modules and kernel]).

For sure, that's where something like rhai would shine: https://crates.io/crates/rhai

Oh yeah, for sure. But there are rust based scripting languages that are designed to interop with rust, such as rhai: https://crates.io/crates/rhai

Markdown support Markdown as a templating language is supported, and you can use global and local configs. Also, there are several built-in helpers, and you can make your own, in the language rhai

I came across this library lately which might be close to what you’re looking for: https://github.com/rhaiscript/rhai

This is exciting.

I've not had problems with latency in fish, but the promise of rust is that there is so little latency that it heralds a close to the metal feeling I've not seen in decades.

I think that feeling is visceral and laudable, regardless of the actual runtime profile. It's under-appreciated in the design community. IPC latency is as big a problem in operating systems and programming languages as RPC latency is in cloud systems.

I have no experience with rust, but I do depend on helix daily:

https://github.com/helix-editor/helix

and helix is rust.

I think this kind of open source experiment is exactly what we should be encouraging because it's forward-looking and straightforward to test.

I think the fish community could decide easily by A-B testing the Rust and C++ builds with real users and see how they compare in terms of reliability, performance, regressions, time-to-fix, and so on, assuming the team has the bandwidth to absorb the sideways nature of the work without derailing fish.

To me, rust is more than trendy and I can remember the first time I touched Walter Bright's work decades ago, so I'm open-minded about D too. A simple KLOC or cyclomatic complexity as a proxy to abstraction would be an interesting lens.

Once https://github.com/helix-editor/helix/pull/5420 lands adding folding should be pretty straight forward

There's no way to refer to any context from the current Helix session in the command invocation. If you want to refer to the path of the current file, you have to type it out yourself. Command substitution would make it way more convenient to use the family of shell commands (:sh, :pipe, :insert-output, :append-output). Thankfully there's a Pull Request out for it already.

There was https://github.com/helix-editor/helix/pull/4649 for an integrated terminal. Sadly the author stopped working on that. An integrated terminal does fit in core and something we would like to see eventually. Maybe someone is able to pick that work up.

- **tree explorer** : previous attempt https://github.com/helix-editor/helix/pull/2377 and now this https://github.com/helix-editor/helix/pull/5566 We all need it

[2]: https://github.com/helix-editor/helix/pull/3890