When I moved away from Scala and got into Haskell, I couldn't believe how much easier Haskell makes programming for me thanks to its type system. This shift opened a whole new world for me.
Now I'm experiencing the same, but within #Haskell: seeing how #Yesod fails to utilize the type system, which leads to opaque and repetitve code in programming a #web #api, whereas #Servant provides structure, clarity, documentation and other via types.
Types for the win!
@mdimjasevic Glad to hear that from someone else. It's very close to my own experience actually, but the very positive way i hear most of the web talk about Yesod makes me doubt how well founded that feeling is sometimes.
However, when I have to modify an endpoint, with #Yesod I'm lost as to what are the constraints for the endpoint. What I've seen so far with #Servant seems to solve these problems elegantly by relying on the #typesystem. Furthermore, Yesod conflates different levels of abstraction, which makes it even harder to see what is going on and where.
@mdimjasevic @tauli In most cases inference and typed holes is quite helpful when you need to figure out the types. Wrote quite a lot of production Yesod, but I'm with out on the Servant thing. Yesod is very opinionated and wants you to adhere to these opinions. Working with servant is a lot more liberating.
Mamot.fr est un serveur Mastodon francophone, géré par La Quadrature du Net.