3 ms·
> Maybe these tools are useful if you already understand them in detail, but for someone familiar with Haskell but writing a web application with it for the fir
by ghostwriter 6y ago
> Maybe these tools are useful if you already understand them in detail, but for someone familiar with Haskell but writing a web application with it for the first time, this experience isn't even on the same scale as a good, production-ready ecosystem.
But this is hardly an example of "not being able to find it with a search engine" as the original message seemed to claim. Surely it takes time to get acquainted with a new ecosystem, and curiosity is welcomed in the community.
> To discover what is actually possible in this area, someone new to Yesod is supposed to read the entire book through to an appendix
That's hardly true either, one just needs to google "haskell yesod http2" or "haskell yesod tls" - both results will be within topmost 5 links. The results will be full of potentially unfamiliar technical details, but they still allow getting the general idea of what is possible. And reading the book helps enormously to get everything internalized.
> There's no further information on those documentation pages about how to actually use important features of HTTP/2, for example setting up server push, though
the top link of googling "haskell warp http2 server push" produces a whole section on how server pushes are done -
https://hackage.haskell.org/package/wai-3.0.4.0/docs/Network-Wai-HTTP2.html https://hackage.haskell.org/package/wai-3.0.4.0/docs/Network...
> in some other search engines such as Duck Duck Go
I use DDG by default, and I regularly add !g for the same reason
- user5994461 6y agoI tried too and there was nothing useful I could find in the first results of google for "haskell yesod http2". Google is heavily customizing search results per use so we probably have different results. The only related thing I got at the end of search results is this page https://www.yesodweb.com/blog/2015/07/http2 https://www.yesodweb.com/blog/2015/07/http2 that doesn't even mention yesod so good luck trying to understand what is it while all it talks about is haskell warp. By the way this paragraph is scary. Haskell didn't support half of the modern cryptography required for TLS 1.2 (2008) so the author had to write them himself (and sent pull request to the tls haskell package). "Unfortunately, many pieces were missing in the tls library. So, it was necessary for me to implement ALPN, ECDHE(Elliptic curve Diffie-Hellman, ephemeral) and AES GCM(Galois/Counter Mode). They are already merged into the tls and cryptonite library."