Ben Jeffery

Great, was thinking that would be the first workflow to optimise, and doing just that one first makes sense. > I guess we could mark the input TableCollection as read-only...

#1566 won't help here, unless we specifically write it to detect it is running in Pyodide. This is because you can't open sockets like normal Python due to the web...

I don't that the faffing there is so bad. Jupyterlite is always an option.

Just `k` or `M` would avoid having to be specific but still easily understandable I think.

We have https://github.com/tskit-dev/tskit/issues/2176 planned (soon) to bring the new C variant methods up to Python. After this, it will be pretty easy to make convenient methods on top. What's your...

I would hope before the paper release! So a couple of months?

Thanks for spotting this @hyanwong - I've added this to the metadata project. We'll soon take all the metadata issues and plan out a coherent high-level API for the schemas.

I'm still not sure about having `draw` and `draw_svg`. It feels like this is confusing as the difference isn't clear from the names. But I agree that if we can...

> Also, support for unary nodes would be good (but I suspect this will happen automatically) Yes, thanks! Added to the list. @hyanwong @szhan do you have anything to add?

> I made this point somewhere else, but the ability to parse into a table collection would mean that we could cope with zero-length (or even negative-length) branches. What would...