Rust is not a low level language is a high level language like C/C++. It belongs to the special category of system programming languages, languages designed for the creation of OSes which is not the main focus of low level coding itself. Low coding is about direct access to the hardware. The only low level language I am aware of is Assembly, low level essentially means that it maps one to one with the hardware architecture. Essentially you don’t execute programming command but rather machine code instructions that look a bit English like.
Compilation checks , especially on data types is a highly debatable and biased argument that dynamic languages have been winning for a long time now judging from their increase in popularity proportionate to the increase of popularity of static languages like Rust , C/C++. Bottom line is that even a compiler as sophisticated as the one used by C++ is not smart enough to captures errors when data becomes highly dynamic. Dynamic data is also very popular in C++ through the usage of templates and in other language through the usage of generics. To make matters worse , Python now comes with optional static type declaration so essentially the argument of static vs dynamic is kinda pointless nowadays. As a matter of fact if one chooses to make C/C++/Rust code as dynamic as Python code, not only he loses the advantages of static type checks but more so will experience even worse performance than CPython. Hence why Rust makes a poor replacement for Python even though it may be good replacement for C++.
Problem with Rust is that it will take a Rust developer to pull it through and they are not many, more so Rust even though looks promising is still slower than C/C++ in some tasks. Even bigger problem is integration with libraries and existing C/C++ code even though language promise integration in reality it tends to be cumbersome. Top performance and high library integrations are huge priorities for Blender.
On the matter of Python performance it does not matter as much as you may think it does. Blender itself uses Python just to setup its UI so it does not affect the performance. The only problem exists for addons , but clever addon development depends on high performance libraries like numpy that are written in C and is included with Blender. Because much of the heavy lifting happens at C its kinda rare to experience a slow down because of the API, but you will experience in your own python code if you rely too much on pure python code for high performance tasks.
In any case addons are ill equiped to handle such tasks anyway , because optimal performance would required direct access to Blender source that the addons do not have. Hence many addons that aim for highest performance either rely on C/C++ libraries or end up being included as source code in Blender source or exist as seperate forks. An addon example of being included in the blender source is of course the very usual suspect, pie menus. Python code turned into C code that fully leverages the Blender internals. An example of an addon that was not included in the source code and became a fork, is Fracture modifier.
So in any case Rust does not offer to Blender anything that tempting and is highly unlikely it will be embraced as language any time soon. As a matter of fact the majority of Blender code is not even written in C++ but in C, making Rust even less appealing which is more a C++ alternative than a C alternative.
On the other hand, Blender is free software and you are more than welcomed to make your own fork and port to whatever extend you want its code to Rust. This is the best way to convince developers to join you if you can prove that your Rust port is more fast , as compatible , as highly flexible and stable. Because in that case your wont be arguing an opinion , idea or “fact” but rather have the proof to prove so.
