Mainly, I believe that most the energy put in Yesod goes on the problem I find the most important.
- Security by default, directly imported from the Haskell type system.
- Fast, also, because Haskell is quite fast compared to most languages used for the web.
- Able to manage a lot of concurrent connexions,
- Incredible foundation language, Haskell is simply awesome (look at my latest blog post for details[^1]).
On the other hand, IMHO, the future of the web might be:
- an API server as good as possible (fast/distributed/clever)
- many good quality dynamic (and generally native) clients
Therefore, I find most of the effort put in the HTML/CSS/JS generation while impressive not so essential for what I look.
On the other hand, the notion of Yesod's widget is a very clever first step in the direction of web component abstraction.
So in conclusion, yes, Yesod went a step further from what I expected from server side web technologies when I discovered it.
- Security by default, directly imported from the Haskell type system.
- Fast, also, because Haskell is quite fast compared to most languages used for the web.
- Able to manage a lot of concurrent connexions,
- Incredible foundation language, Haskell is simply awesome (look at my latest blog post for details[^1]).
On the other hand, IMHO, the future of the web might be:
- an API server as good as possible (fast/distributed/clever)
- many good quality dynamic (and generally native) clients
Therefore, I find most of the effort put in the HTML/CSS/JS generation while impressive not so essential for what I look. On the other hand, the notion of Yesod's widget is a very clever first step in the direction of web component abstraction. So in conclusion, yes, Yesod went a step further from what I expected from server side web technologies when I discovered it.
[^1]: http://yannesposito.com/Scratch/en/blog/Haskell-the-Hard-Way...