I'm partial to rust. I think the borrowing is a good addition to the memory model and stepping back on class hierarchies (inheritance) are very nice aspects, and i would like to see them in whatever general purpose high performance language id like to use in long term. But the two issues i have with rust today are
a) if you want a personal problem - *if* a language is so obviously inspired by c/c++ syntax, why so deliberately introduce some constructs that seem just alien to that style (if b is solved i guess i can get used to it over time, but reading doc today for a prospective language to get used to, there seemed to be far more WTH are you thinking aspects that eg java and c# introduced over a long time)
b) (actually somewhat on topic) no way i'm voluntarly investing in such a moving target as rust appears today. The projects i care about are measured in decades. At job i maintain pre c99 code, c++ that kinda compiles on semi modern visual studio but was written for vs2003, and a project from ground up written in std c++14 as cutting edge. Some used libraries were ported from the 1970 or maybe even earlier. Now that's the job, but my hobby project is also largely in that dimension, its' mostly c++ today and i rewrite some algos from 10 years ago, but introducing a new language to take over even parts of what modern c++ can do well today required some confidence in there being real benefits (the private project is RAII, make_shared and stack variables; you could say HPC, afaict no memory violations in lots of allocations - no idea about numbers, running even a desktop ryzen at full tilt today rips through terabyes of memory in no time) and language stability. In some parts i feel c++ is dragging, in other parts i also think the standard is moving rather fast. Now for rust, once there is a proper versioned standard (written down as standard, preferably ISO, but IETF, IEEE, EMCA etc ok fine) where you can expect to still be able in 2035 to compile a large code base wtitten in standard rust version 2024, yes let's go. absolutely.
But while people are committing to a language that in a way still tastes like some ephemeral move fast break things before the first coffee in the morning github project. Well. Not surprised.