fish-shell

They are the author of the project. So, I guess the idea is that they want to make future development and maintenance easier. It also probably isn't in their interest to split the community (Also, as a fish user, I also personally wouldn't like if the community split) Edit more here: https://github.com/ridiculousfish/fish-shell/blob/riir/doc_i...

That's different than what they say in their high level planning doc. https://github.com/ridiculousfish/fish-shell/blob/riir/doc_i... > Allowing background functions and concurrent functions has been a goal for many years. I have been nursing a long-lived branch which allows full threaded execution. But though the changes are small, I have been reluctant to propose them, because they will make reasoning about the shell internals too complex: it is difficult in C++ to check and enforce what crosses thread boundaries. > This is Rust's bread and butter: we will encode thread requirements into our types, making it explicit and compiler-checked, via Send and Sync. Rust will allow turning on concurrent mode in a safe way, with a manageable increase in complexity, finally enabling this feature.