Michael Droettboom

> > Given #117123, and the performance regression, maybe it makes sense to revert #116206 while working on getting this right? > > Why not merge this PR? Your numbers...

Looking deeper at the benchmarking data for this PR vs. the commit prior to #116206, memory usage is up pretty significantly for the benchmarks that actually have a lot of...

> OOI, how much in absolute terms? A relative increase in memory isn't that meaningful. Here's the absolute numbers. I think what really matters for this is to ensure that...

> I'm going to merge this, as it does fix the immediate problem. Ok, and you are going to fix the pystats build as a follow-on, rather than addressing here?

You make some good points. I think there's a couple of different frames of reference here. If the goal is "how fast is CPython at importing all this code?", copying...

`wasmMemory` is the memory buffer for the running wasm code. A `wasm` file is WebAssembly bytecode. I don't think the two are interchangeable like this. Have you seen [wasm-persist](https://github.com/dfinity/wasm-persist)? I...

First -- I should have said before that this is something I'm really excited to see being worked on. I've thought about something like this for a while but haven't...

There was some abandoned work to get this done by replacing `FT2Font` and `ttconv` with a more modern freetype wrapper that gives us what we need to do the font...

You can read MEP14 : https://github.com/matplotlib/matplotlib/wiki/Mep14. It actually has a much larger scope than just this -- the relevant sections to this bug are "Font subsetting" and "Freetype wrappers". Essentially,...

> @mdboom Are you okay with me editing your topic to create a checklist style table with links to either why we're not implementing or the actual implementation? My guess...