I guess I see what you mean if we want to get very technical about what a syntax extension is. But I think for the purpose of this discussion, it's reasonable to think of macro_rules! as a part of the Rust language. Practically speaking, it is syntax provided by the language team, not just users of the language who are free to extend the syntax by usingmacro_rules! to do so.
Enums are the best part of the Rust language IMO, so I'm not sure how you can view them as ugly. Having the choice to destructure something is fantastic. You generally aren't required to destructure every return value. Make sure you're using the ? operator as much as possible. If destructuring is getting in your way, it sounds like the code is not very idiomatic.
I can't really comment on your issue with nested if and match. Too much nesting is bad in any language; try extracting more functions and let bindings to make it more readable.
You can enable a clippy lint to deny .unwrap() if you're worried about it.
Sorry, I love Rust but I can't really agree with you here. They only showed a macro_rules!definition, which is definitely rust syntax. Lifetime annotations are relatively common.
I will concede that loop labels are incredibly rare though.
It's sad that self-hosting is apparently the path to having a solution that "just works". You'd think that paying for a product would be more effective, but alas...
I don't have first-hand experience, but I've heard that the linux version of MakeMKV does work; though I've seen some issues reported in the forum. MakeMKV is even available on nixpkgs.
I don't know about MicroSD longevity, but I've heard BluRay and in particular M-Disc can last 100-1000 years of something crazy. So for archive, it might still be a good option.
I really hope streaming doesn't become the only option, because even with >1Gbps internet, streaming services generally do not deliver as good of quality as I can get from something like a bluray. Even HBO and Netflix have very noticeable lossy compression.
I guess I see what you mean if we want to get very technical about what a syntax extension is. But I think for the purpose of this discussion, it's reasonable to think of
macro_rules!as a part of the Rust language. Practically speaking, it is syntax provided by the language team, not just users of the language who are free to extend the syntax by usingmacro_rules!to do so.