Awesome work!

In unrelated note.. I am working on a ts/js wrapper for llhttp as I mentioned and will for now use wasm memory, but just copy the buffers back and forth. It will be a bit less efficient, but still a lot faster than parsing http in js.

Awesome work!

In unrelated note.. I am working on a ts/js wrapper for llhttp as I mentioned and will for now use wasm memory, but just copy the buffers back and forth. It will be a bit less efficient, but still a lot faster than parsing http in js.

Nice! What would you need to have optimal performance? the Memory implementation?

Awesome work!
In unrelated note.. I am working on a ts/js wrapper for llhttp as I mentioned and will for now use wasm memory, but just copy the buffers back and forth. It will be a bit less efficient, but still a lot faster than parsing http in js.

Nice! What would you need to have optimal performance? the Memory implementation?

Don't spent much time on Memroy - If I find a real use in the wrapper and meaningful performance improvements I will ping you. Again awesome work.

P.S. I have always liked quickjs but as a "raw" runtime it is lacking a lot of required features to make it useful for anything more than scripting. With txiki.js it is completely different - this thing is a full blown runtime quite comparable to node. With a little more ecosystem around it, txiki.js can be the embedded king if you want to use js instead of python/micropython or go native.

Thanks for the kind words!