So the way I'm looking at this is kinda like this. Imagine you're a chef, used to cooking with a classic set of kitchen tools--knife, pan, stove, etc. Those tools are straightforward, give you direct control, and have been used forever. There's countless recipes, tips, and communities built around these traditional tools.
Now, suppose you're given a high-tech, modern cooking gadget like an InstantPot or some shit that promises to make cooking safer and more efficient. This gadget has features to prevent common kitchen accidents and ensures your food is cooked perfectly every time. However, learning to use this gadget is like learning to cook all over again. It's complex, has many rules, and you can't just jump in and start cooking the way you're used to. Moreover, the new gadget might not yet have all the attachments you need for every recipe, and there aren't as many cooking guides or experienced chefs who can help you troubleshoot when something goes wrong. Some cooking techniques that are easy with your traditional tools become cumbersome or less intuitive with the new gadget. Idk, probably a shitty analogy, but my point still stands.
Rust has a steep learning curve due to its strict ownership model, lifetimes, and borrowing rules, so that makes it difficult for new developers or those transitioning from other languages like C to pick up and use effectively in OS development, IMO. While Rust is rapidly growing, the reality is that the ecosystem is still relatively young when compared to more established languages like C and ASM. Some OSDev tools, libraries, resources, etc might be lacking/less mature. Another thing to note is that while Rust provides a lot of safety features, it can sometimes abstract away low-level control that's crucial for something like OSDev. Certain operations may be more cumbersome or less intuitive when compared to C, where the dev has more direct control over the hardware. The other main consideration is the the OSDev community has a long history with languages like C and ASM, so there's wayyyyyy more resources, examples/code snippets, helpful forum posts, etc. Using Rust you'll absolutely encounter way fewer examples and less OSDev community expertise. Idk, all in all, while there are successful projects, Rust just isn't battle-tested for OSDev yet and you'll probably run into a lot of issues and/or limitations. I'd say just know what you're getting yourself into, really.
All that being said, Rust does of course offer a lot of nice perks, like memory safety, concurrency safety, and modern tooling. I'd say if you're willing to stick it out and inevitably deal with some really annoying shit, then go for it. Just my two cents.
