cryptonite VS wai-conduit

There was also the Haskell-crypto fork (https://github.com/haskell-crypto/cryptonite) which was done for similar reasons - will this fork include any of its changes? I can’t remember if much was actually done in that project, most of the work has been on the libsodium library. It would be good to have just one place for all of this, perhaps Kazu could consider moving crypton into that organisation and helping contribute.

GHC 9.2 support for cryptonite is added in this PR: https://github.com/haskell-crypto/cryptonite/pull/354 So that should be fixed soon i guess..

fromIntegral is no joke, for example https://github.com/haskell-crypto/cryptonite/issues/330

The main issue is actually inability to switch to newer GHC 9.0, which seems blocked by other packages

found some context https://github.com/yesodweb/wai/pull/931

Yes. Not because of the developer, but because of how extremely flexible and dynamic the Lisp-family languages are. The power and joy of Lisp is in how it's almost a meta-language, so every project can become its own EDSL. The most famous (infamous?) example of this is Vacietis[2], which is a Common Lisp library that allows C code to be imported directly(!!).

[0] IIRC the Yesod framework's Warp does well on benchmarks, and when you look at code like https://github.com/yesodweb/wai/blob/master/warp/Network/Wai... you can see the lengths they had to go through to work around the choice of implementation language.

[1] Go has a garbage collector, but exposes the stack/heap distinction more directly than Haskell, so it's easier to write allocation-free code in hot paths.

[2] https://github.com/vsedach/Vacietis

I switched backends a bunch of times because everything I tried (Go stdlib HTTP, Tornado, etc.) kept getting taken out whenever I would hit the front page, either due to CPU overload or some sort of resource leak. I ended up using Warp+Wai+Servant (https://github.com/yesodweb/wai) and it has been smooth sailing since then off my $3/mo VPS. It can take thousands of req/sec without flinching (which is higher than what you see from top of HN - that maxes out at a few hundred req/s).

My $3/mo vultr box can handle HN loads easily when using a fast backend (I've settled on https://github.com/yesodweb/wai based apps - the only thing that has worked well for me so far).

What kind of metrics do you derive "ton of stuff" from? It seems like the largest blocker is Cryptonite. It's unreasonable to let a handful of packages keep back Nightly. You can now run Warp without it. How does your list of essential blockers for 9.2 look like?

Is this the correct repo? https://github.com/yesodweb/wai

No, Wai is the common abstraction, sort of like connect. Warp is one (only AFAIK) server implementation of it. Both Wai and Warp are developed along side with Yesod, you can find their source code here https://github.com/yesodweb/wai

WAI