Large parts of the rewrite came from contributors who had never worked on fish before.
That’s pretty useful alone.
And there’s this:
Thread Safety
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.
Vibes are just as important to free/open source software as proprietary software and although there were solid technical reasons for the port, the PR outcomes are added benefits.
The time spent re-writing it in rust could have been spent doing that in C++… But whatever. They can, and will, do whatever they want. Even if it’s “for the vibes”.
Except the devs wanted to write it in Rust, they didn’t want to continue writing C++. It’s as simple as that. There are also issues that they hope to fix using Rust that would have taken a huge amount of work using C++.
I read that, but I still disagree with your sentiment that they “could have been spent doing that in C++”. No devs wanted to do it in C++, so it was never going to be done. Switching to Rust, where people will be willing to do it, makes much more sense.
Probably not “angry” downvotes. OP provided a link where it’s explained exactly why the switch was made. Even if you don’t care for Rust it’s pretty clear that this was done with more purpose than just “Ooo let’s make it in Rust for fun”
These rewrites in rust are merely just training exercises for those doing it. It wasn’t needed and in most cases isnt used.
That’s pretty useful alone.
And there’s this:
They did it “for the vibes”
They also did it to hopefully add concurrency.
The time spent re-writing it in rust could have been spent doing that in C++… But whatever. They can, and will, do whatever they want. Even if it’s “for the vibes”.
Except the devs wanted to write it in Rust, they didn’t want to continue writing C++. It’s as simple as that. There are also issues that they hope to fix using Rust that would have taken a huge amount of work using C++.
I read that, but I still disagree with your sentiment that they “could have been spent doing that in C++”. No devs wanted to do it in C++, so it was never going to be done. Switching to Rust, where people will be willing to do it, makes much more sense.
It was needed to safely further support for concurrent features? If they follow through on adding that support, there will likely be adoption.
The problem is in most cases the implementers stop at “same thing but in rust” without taking advantage of that.
I can’t fully blame them since just duplicating an existing thing is a huge undertaking.
Angry downvotes because people don’t like to hear that a meme language is a meme language.
Meme language? It was not rewritten in Javascript.
Probably not “angry” downvotes. OP provided a link where it’s explained exactly why the switch was made. Even if you don’t care for Rust it’s pretty clear that this was done with more purpose than just “Ooo let’s make it in Rust for fun”
And even if it was for fun, that would still be valid. The project is run by volunteers. If they don’t have fun, they stop doing it.
Didn’t this “meme language” ship in a recent Linux kernel?
You clearly don’t know what a meme language is.