You dont. Thats why you write code that explains itself. For higher level info you write documentation.

Microsoft be like

I once heard that a major problem is that you have to disable or work around Rusts safety features once you write hardware interfacing code like a os kernel

Why would you say that Rust is made for low level hardware interfacing? I am generally curious.

All these concepts like optional markupfiles, identifying objects by id, creating objects from markupfiles and WYSIWG editors also exist for the xaml(which is a Dsl) and C++ stack. Its just that microsofts usage and tools are crap like every other microsoft software

Thats how every GUI which is not immediate mode works. Are there any examples where it works different?

If it works, it works

Dynamic typing, special and unique syntax for every language feature, interpreter intrinsics

If you compile on windows server the same problem happens. The server is basically gone. So there seems to be some special scheduler configuration in windows client os.

lIIl, IIIl, lIlI and IllI

I guess you ask for C++. There Type* can be null while Type& can’t be null. When it gets compiled Type& is compiled (mostly) to the same machinecode as Type*.