scenewriter VS tpr

I wrote a thing in Rust, and got excited about being able to wasm-pack it and run it in a web frontend. In Firefox on my laptop it runs fast, it's like 2.5x slower in Chromium, which is still kinda OK. Then I tried it on my not-new-but-not-that-old tablet and IIRC it was something like 50x slower, which is not really OK.

Oh, I think I might've come across screenplain but been put off by "PDF will hopefully be supported in a not too distant future" in the README. The rest of the README suggests we're already in the not too distant future. I might not have bothered to write Farce if I'd known.

First Rust project, a fountain screenplay markup parser called Farce.

Hey, this might interest you, as a similar thing could be implemented as bridge between freenet and the clearnet. I've been working on this for a while now. https://github.com/Alonely0/tpr

I'm throwing away all the code I had written and implementing my TPR protocol from scratch, I'll be using tower this time, lesson learned...

I'm more of a pomegranate guy

I'm implementing tpr, so I'll definitely take a look at this

Lariv is a thread-safe, self-memory-managed vector with no guaranteed sequential insert. It internally uses a linked ring buffer, that unlike traditional ring buffers, is growable, and very importantly, it doesn't reallocate the whole buffer as part of the process. It has been born inside the TPR project, and it is designed for storing client connections on TPR servers, which usually are short-lived data that have to be accessed via 128-bits integers. This is basically the dashmap for vectors.

In my case I use IDs for pairing multiplexed connections to encryption keys. I'm implementing The Pomegranate Router.