Sounds like these 80 year olds need some friendly data hoarders to help them to digitise their collections. (Or for the BBC to promise to return the film, undamaged, once they’ve digitised them.)
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.
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.
Why would the BBC want old film, once they had the footage? They’ve already thrown them away once! It’s only of value to collectors at this point, and the Beeb can’t sell it if they’re claiming it’s lost.
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.