Librsvg did the rewrite incrementally, so you can choose to only use rust for new code in an existing codebase.

The borrow checker handles more than just freeing allocated memory, it will also prevent data races and invalid concurrent access aso. I personally don’t have any issues with using garbage collected languages, but the fearless concurrency is nothing I’m willing to give up.

If I look at what I use and what annoys me, I would have like to see focus on ‘Dyn async trait’ and ‘Traits for being generic over runtimes’. I think it is quite annoying that you have to decide on a whole eco-system when you are doing async code. I have had times when I have search for a very niched library, only to find that it is written for the wrong async runtime. And the longer it takes to correct this, the more cemented it will be.

Have you tried to run it as root?

I see this post as an advice to learn gradually, and to write sloppy but painless code initially. Then when you have the basics, you can add the more idiomatic and tricky parts.

Why are you doing

cards.iter_mut().for_each(|card| {

I don’t see that you mutate card anywhere, am I missing something?

Just looked at the screenshot on the Victor Mono page and the kerning makes me want to rip my eyes out…

Ok, after reading some comments on other places, I think I get it now. While you are free to use their open sourced tool chain, which is what they have certified, you still doesn’t fulfilling the legal requirements unless you buy the certified tool chain. Just because it is open source, doesn’t legally guarantee that is what’s certified.

So, you pay to get the legal status of the certification. Did I understand this somewhat correct?

I must say I am a bit confused. They are open source, and some previous blog post said they are certifying upstream. Yet, they sell quality managed licenses. So, what are these licenses and why are they needed?