I think it was originally written in C, and it apparently approaching being fully Rust.
Rust claims very loudly, repeatedly, and apparently with honesty that "gotta go fast" and safety are language design goals and features. So I'd imagine even a developer who just wants to get their hands dirty with Rust would be willing to do battle with the borrow checker since there's a good chance they'll eventually hit those goals that they share in common with the language itself.
Does Haskell have "gotta go fast" as a central language feature? If not, that'd be a real gamble for an SVG renderer. After all, what's the use of a library that produces the output you'd expect, but also at a speed you'd expect for a kludgy, over-engineered, text-based vector image format?
> But everyone still shits on "Rust Evangelists" when they bring it up.
Yes, but the language forces them to shit on it for reasons other than "not being fast." :)
librsvg is one.
I think it was originally written in C, and it apparently approaching being fully Rust.
Rust claims very loudly, repeatedly, and apparently with honesty that "gotta go fast" and safety are language design goals and features. So I'd imagine even a developer who just wants to get their hands dirty with Rust would be willing to do battle with the borrow checker since there's a good chance they'll eventually hit those goals that they share in common with the language itself.
Does Haskell have "gotta go fast" as a central language feature? If not, that'd be a real gamble for an SVG renderer. After all, what's the use of a library that produces the output you'd expect, but also at a speed you'd expect for a kludgy, over-engineered, text-based vector image format?
> But everyone still shits on "Rust Evangelists" when they bring it up.
Yes, but the language forces them to shit on it for reasons other than "not being fast." :)
Edit: clarification