cpp-vs-rust VS tiny-skia

> They seem to have chosen to use mold for C++ and not for Rust after seeing that it gave little benefit for small projects, but I would expect that to change as the project scales.

The benchmarks show Mold for both Rust and C++. This wasn't explicitly stated in the article; sorry. https://github.com/quick-lint/cpp-vs-rust/blob/f8d31341f5cac...

Very well-researched article (in my uninformed opinion because I've done virtually no benchmarking). I'd summarize it as, Rust doesn't significantly improve build times over C++ for a project where you need to frequently recompile to test the logic of the code. I gather that the Rust code is pretty idiosyncratic (using raw pointers rather than slices and custom owned and borrowed string containers with i32 length and capacity fields), but I don't know why more idiomatic Rust code would be faster to compile, and it could be very different, so a worse comparison. The results aren't relevant for me because I use Rust mainly for the language features and don't have a project with terrible compile times or the need to often rerun tests, but there might be other C++ projects in the same boat as quick-lint-js that would consider moving to Rust if it compiled faster than C++. Hopefully the efforts of people like u/nnethercote will make that happen.

You can even check https://github.com/linebender/piet and https://github.com/RazrFalcon/tiny-skia. They are pure rust libraries. Skia as a whole is a big binary to add.

Looking through the source code. It looks like it's using tiny-skia for rendering.

Tiny Skia (https://github.com/RazrFalcon/tiny-skia) which is a slower Rust port of Skia and does all software rendering.

https://github.com/RazrFalcon/tiny-skia is pretty great.

I understand that this may sound harsh, but I also ported two (far bigger) codebases from C++ to Rust: rustybuzz and tiny-skia. Both of which are production -ready and not just prototypes. And mine not only do not use pointers, but also barely use unsafe in general.

Here is a real world implementation in tiny-skia: https://github.com/RazrFalcon/tiny-skia/blob/master/src/pipeline/highp.rs

How about tiny-skia?

How about tiny-skia? Almost the same performance as C, no unsafe, a lot of explicit SIMD.

Now I would love to see a universal Bezier path crate, storage + common utilities like length, point at offset, some low-level stuff, etc. So it could be used as a foundation for other crates. Currently, there is a lot of friction because each crate has its own implementation.

Nice to see tiny-skia in use.