lady-deirdre VS moxie

Well, my personal experience was in the opposite direction actually.

I used to use combinators-based approach without Lex/Syn separation (aka PEGs) for a long time. But then I came up to understanding that the separation approach is actually better in performance. And also that working and debugging of the Token sequences while writing parser manually is just more handy (at least for me).

But this is my personal experience of course. I do believe too that it all depends on the goal, and parsers micro-optimizations is not that much critical in many cases, and that combinators approach actually works quite well too.

As of Nom, I can say that it works quite well. But I think that the it's performance gains stem from the fact that Rust is a systems-based PL, and it optimizes function combinations just better than, let say, JavaScript or Python.

In my incremental parsers library Lady Deirdre I utilize Lex/Syn separation, and the LL(1) recursive-descend parsing, and it shows much better performance than in Tree-Sitter at least on relatively big files [1].

[1] https://github.com/Eliah-Lakhin/lady-deirdre/tree/master/wor...

I think https://moxie.rs/ as well

That's the idea of azul and moxie-native: they use web technologies but are way lighter than embedding a browser.

There are various ways you might do an implicit context objects. An example is the illicit crate, from moxie.

Rather than using a macro based DSL, it uses plain rust syntax with a builder pattern inspired by Moxie. It's inspired by Solidjs and Maple on the signals/reactivity side.