Sprache VS Stateless

Sprache

Unfortunately I'm struggling. The first problem is choosing which combinator library to go with: Sprache, Superpower, Parlot, Pidgen, Lexepars, etc. etc. Some look simpler to use than others, others more performant, others come with useful parsers built in.

I found Sprache much easier to learn/use than FParsec.

Things like https://github.com/sprache/Sprache are arguably similar.

Att my office usually use Sprache to parse complex models from strings. Mostly query expressions, but it should excell at parsing html as well. Maybe it can be a solution for you here. https://github.com/sprache/Sprache

I like this method and state machines in general. Makes it more easier to reason about complex software. Also, ithe f the state machine gets bigger (more states) in the past I have used the Stateless library which is very good. But what you described above is perfect for managing the state of a menu system.

After using stateless for three years, my conclusion is that I cannot imagine a scenario, where it makes sense to use it.

This is a great article. Here is the Stateless library he is writing about. The link to the library is kind of buried in the middle of a sentence.

Yes! And we're using one. https://github.com/dotnet-state-machine/stateless We're creating the configuration dynamically based on how the user wants his workflow to work.

Stateless is my go-to state machine library for .NET. It's reasonably advanced but can also be very simple if you don't need the more advanced features.

I'm playing around with this library for a medium sized state machine I'm setting up, and it has this functionality. I think explicit state machines are a good use-case for having an actual diagram, since they can take up enough space that it becomes hard to build a mental map from reading the code due to locality issues.