connection VS wai-conduit

Trying to build the "old" hs-connection (which is still in my my project's dependency tree) after a cabal update, I now get this : Network/Connection.hs:123:43: error: • Couldn't match expected type ‘crypton-x509-store-1.6.9:Data.X509.CertificateStore.CertificateStore’ with actual type ‘Data.X509.CertificateStore.CertificateStore’ NB: ‘crypton-x509-store-1.6.9:Data.X509.CertificateStore.CertificateStore’ is defined in ‘Data.X509.CertificateStore’ in package ‘crypton-x509-store-1.6.9’ ‘Data.X509.CertificateStore.CertificateStore’ is defined in ‘Data.X509.CertificateStore’ in package ‘x509-store-1.6.9’ • In the ‘sharedCAStore’ field of a record In the ‘clientShared’ field of a record In the expression: (TLS.defaultParamsClient (fst cid) portString) {TLS.clientSupported = def {TLS.supportedCiphers = TLS.ciphersuite_default}, TLS.clientShared = def {TLS.sharedCAStore = globalCertificateStore cg, TLS.sharedValidationCache = validationCache}} | 123 | { TLS.sharedCAStore = globalCertificateStore cg | Error: cabal: Failed to build connection-0.3.1.

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

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?

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