It is _quite_ different than the ASPX web forms or XML web services I cut my teeth on; to use this framework for a side project, I'm needing to teach myself both ASP.NET Core and MVC-style development at the same time as continuing to get comfortable with F# & Giraffe's own syntax.
I may or may not have bitten off more than I can chew, but between the existing ASP.NET Core docs and the nice documentation in Giraffe (one big file at the Github repo), I'm not defeated yet.
Thanks for letting me know! I think I'm currently in the throes of "nothing makes sense why do I have to do route vs routef when do I do this stuff why is everything squashed into HttpContext!!!?" dither when I just haven't ramped up the mental framework to reason about what I'm doing. Hopefully, I'm making progress towards there, but at this second, any issues I open would be skewed WAY towards the pedantic/RTM side of things rather than stuff of substance.
But I will totally open an issue if I have something not time-wasting!
This library is what I do all my new web services development in (or it's child Saturn). I'm actively working to migrate my legacy codebases to it. It feels pretty good given the host platform, and is easy to mix and match with non-giraffe components too.
Yes, Giraffe has already taken some lessons from Zebra with some of the recent optimisations around the view engine. I think there are some more immediate gains for routing, but currently the focus is on a great Swagger integration before dwelling into anything else which requires more work. However, PRs are always welcome. To be honest some of the best perf improvements all came from PRs!
[1] https://www.techempower.com/blog/2018/10/30/framework-benchm...
[2] https://www.techempower.com/benchmarks/#section=data-r17&hw=...