3 ms·

You say you can use type-safe urls, but you aren't actually doing it. And the reason why is it isn't supported end-to-end by your framework. You can't stick one

You say you can use type-safe urls, but you aren't actually doing it. And the reason why is it isn't supported end-to-end by your framework. You can't stick one in a Heist template, and your routing code would become more tedious because routing is not completely trivial. But Again, this is just one example. In your case I doubt any benefits you would receive from switching to Yesod would overcome your switching costs. I would love to have a reasonable discussion about it. But you chose to give us zero feedback until we make a 1.0 release announcement (which means we are going to now limit our changes) and then come out of the wood-work and pic at every nit you can find in the comments of the release announcement and state some other framework is better. Stopping by #yesod to discuss, criticizing on the mail list, or helping your own favorite framework reach 1.0 would be a lot more productive. Edit (because I can't reply): Thanks for bringing up issues on IRC. If you ask on the mail list you are guaranteed a thoughtful answer. We push users towards Hamlet in part because of the type-safe url support, but you are definitely welcome to use any template language you want.

cies 15y ago
geek-slapping the troll :) +1 [EDIT]: should not have posted this.
papsosouid 15y ago
>You say you can use type-safe urls, but you aren't actually doing it I'm not because I don't want them. If I did I would be using blaze-html and web-routes. >But Again, this is just one example. I politely and genuinely asked that you provide those other examples, as the one you did provide is obviously bogus. >But you chose to give us zero feedback until we make a 1.0 release announcement Actually, I did ask in IRC about a year ago. And two days after I asked you offered up the same response you have been giving here: "hamlet is perfect and you are wrong for not liking it". I also got similarly slow and unhelpful responses with other issues, like how yesod used to only work on ipv6. >and then come out of the wood-work and pic at every nit you can find in the comments of the release announcement and state some other framework is better If you were a little less defensive and a little more reasonable, you might see that I never said anything of the sort.

cies 15y ago

geek-slapping the troll :) +1 [EDIT]: should not have posted this.

papsosouid 15y ago

>You say you can use type-safe urls, but you aren't actually doing it I'm not because I don't want them. If I did I would be using blaze-html and web-routes. >But Again, this is just one example. I politely and genuinely asked that you provide those other examples, as the one you did provide is obviously bogus. >But you chose to give us zero feedback until we make a 1.0 release announcement Actually, I did ask in IRC about a year ago. And two days after I asked you offered up the same response you have been giving here: "hamlet is perfect and you are wrong for not liking it". I also got similarly slow and unhelpful responses with other issues, like how yesod used to only work on ipv6. >and then come out of the wood-work and pic at every nit you can find in the comments of the release announcement and state some other framework is better If you were a little less defensive and a little more reasonable, you might see that I never said anything of the sort.