Nice work. Having written a few WAFs for unpopular languages, I think it's most compelling to also include a more stable/mature backend like FastCGI in addition

Nice work. Having written a few WAFs for unpopular languages, I think it's most compelling to also include a more stable/mature backend like FastCGI in addition to the self-rolled socket driver -- similar to how Flask has the dev server and WSGI backend support. If your socket driver (and HTTP parser) ends up being more performant and stable, that's awesome. But it's probably unlikely and definitely a harder sell. FastCGI in particular has the benefit of being incredibly simple to wrap. Here [0] are some rudimentary bindings I wrote for Chicken Scheme. [0] https://github.com/eatonphil/pine https://github.com/eatonphil/pine