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.
Self-hosting email is not at all easy, and I’d recommend paying for hosted email from a service that lets you use a custom domain. Most will let you have multiple inboxes, although this may cost extra.
Then, just buy a domain (NameCheap is fine) and point your MX records at the email provider.
Huh, that’s weird: when I posted, I saw your your comment as a top-level comment but I now I see it as a reply. Maybe it’s a Lemmy bug; I’ll keep an eye out in future.
It is far too confusing what to use - even as someone who uses Linux on various servers, a media centre, WSL and used to run a Gentoo laptop I still don’t know which distro to use, let alone which of KDE/Gnome, X11/Wayland, init/systemd etc.
We had a “kids tape” that had countless things recorded over each other. The second half was just a collage of the tail end of various cartoons and shows. When it got to the Abba-soundtracked documentary about a carnival it meant you were at the end of the tape.