oxide-and-friends VS fontdue

After listening to the Oxide and Friends episode about the Rust trademark dustup I thought some people in the Rust community might be interested in a concept I've been working on for a while called Persistent Democracy.

They've been doing Twitter Spaces for several months now, with recordings and show notes here: https://github.com/oxidecomputer/twitter-spaces Disclosure: I was the main speaker on one of their spaces.

For anyone interested in the history of NeXT, I highly recommend Randall Stross's "Steve Jobs and the NeXT Big Thing."[0] (And I regret that I may have personally had some role in the current outsized prices of used copies -- my apologies!) We also had a really interesting Twitter Spaces discussion of both the book -- and on NeXT more generally.[1]

[0] https://www.goodreads.com/en/book/show/226316.Steve_Jobs_the...

[1] https://github.com/oxidecomputer/twitter-spaces/blob/master/...

Also, where are my manners?! Really glad you're enjoying our Twitter Spaces[0] -- and thank you for the kind words!

[0] https://github.com/oxidecomputer/twitter-spaces

The other alternative is to go a level lower and use something like fontdue and then roll my own font rendering pipe, but that seems overkill for what seems like a simple problem.

I agree that no_std is incredible. I really want to see more crates embrace it and encapsulate their no_std logic away from their standard logic. I very often see crates that are like 95% of the way to no_std but then choose to bundle some standard only features without flagging them.

I wrote fontdue [0] (which is very incomplete spec wise) because there just wasn't another font library that was no_std at that time. It felt like the existing libraries were in an arms race for gpu caches and bundling file loading. Like if I wanted to commit to a running on a platform I'd do the sane thing and use harfbuzz or the platform APIs.

[0] https://github.com/mooman219/fontdue

Like tiny-skia? As for font-specific one there are ab-glyph and fontdue.

I work on a SIMD optimized font library [0] and have stumbled into the same situation of hand writing SIMD intrinsics. Some things are just kinda hard to make sure they get optimized correctly, and there is enough difference between the platforms where that matters when fiddling with bits. I also kinda have fun writing SIMD code like this too.

[0]: https://github.com/mooman219/fontdue/blob/master/src/platfor...

The other library that does a similar thing to ab_glyph/rusttype I remember hearing about is fontdue (https://github.com/mooman219/fontdue)