What about, uh, speed of development, ease of refactoring again, code quality, and contributors? Did RiiR make things better? Worse?

I remember you've shown some examples where Rust clearly made things more concise *and* robust, with error handling around... parsing colors, IIRC? But surely there were opposite examples? What was the ratio?

@bugaevc Woah, there's like eight blog posts in those questions 😄

A retrospective of that kind would be nice. I'll think about it.

my questions are nothing special, really — but if you're feeling like it, then sure, that sounds so cooool, let's do that :)

I'll need to write a more complete / less terse version of the questions then; it's one thing when you're trying to fit thoughts into a toot (and failing, and posting many toots instead 🙃), and another thing when you're writing for a full-scale blog post.

@YaLTeR @alatiera @svenfoo
Here's a sketch of the questions
docs.google.com/document/d/19T…

Had to balance my love for Rust with some skepticism ("supposed", "said to") in order not to sound like the RESF :)

Draft: Questions for the Rustification retrospective

Back in 2016, you have started porting librsvg to Rust. You said that one of the main motivations for the port was improving security, since memory safety-related issues and vulnerabilities were being found in librsvg “every once in a while”.

^{Google Docs}

@YaLTeR @alatiera @svenfoo this is a &mut link -- you can edit / add suggestions / add answers /etc!

Please tell me if Google Docs doesn't work for you, we can do HackMD or HedgeDoc or just Markdown in Git or whatever. Or feel free to just copy over my questions into whatever software you're using to write your posts (which I hope is :D)