Regarding maintenance, syntax is pretty low on my list of "reasons to worry about a language's future". What almost always is at the top is "can I genuinely use

Regarding maintenance, syntax is pretty low on my list of "reasons to worry about a language's future". What almost always is at the top is "can I genuinely use this?" which often means being able to interoperate with other languages and reuse existing libraries, and of course, that the language does what it says it does. In fact, I could only expect more confusion from reusing an existing syntax, no matter how nice it is, if the semantics won't be the exact same. In this case specifically, C# and all its libraries are very much oriented about not managing memory manually, so a lot of language features would either be morphed into something with idiosyncratic semantics, or would not be possible to be used. Maui most likely could not be hacked to work compliantly in a strict realtime environment anyway, for example. So there's no advantage for it to be available.