3 ms·
> has pretty great and clean authentication support. https://docs.servant.dev/en/stable/tutorial/Authentication.. https://docs.servant.dev/en/stable/tutorial/Au
by dmitriid 7y ago
> has pretty great and clean authentication support. https://docs.servant.dev/en/stable/tutorial/Authentication.. https://docs.servant.dev/en/stable/tutorial/Authentication...
> with the availability of parser combinator libraries like Attoparsec.
> you hide these in a config file for your project.
etc. etc.
You're not helping the cause of "this is 99% readable" ;) If you add proper authentication and parser combinators [1], and configs, and.... It becomes anything but readable to a person without specific Haskell and very specific library knowledge.
And yes, I do have exposure to FP having worked with Erlang for a number of years.
I also seriously detest the unexplained love for ASCII art among many lib authors in the FP space. Servant is one such example: :> :. :<|> ! At this point, why not use J :)
[1] By the way, unless I'm mistaken, there's next to zero useful documentation on Attoparsec, there's only barebones package documentation. And no, you don't validate data using parser combinators unless your data is only strings that resolve to some DSL.
- verttii 7y agoWhy would Haskell need to be readable by people who don't know Haskell?
- cerberusss 7y agoWell, it does lower the barrier for entry.
- ulucs 7y agoI want to use J, but I can't unlearn the symmetry of {}. On the other hand, I feel k/q is just too barebones.