11–20 of 113 posts
* Generating migrations automatically when saved may cause some troubles while making large changes. It's a default setting?
* Hamlet seems good but not so obvious for real-world designers. Would be great if you provide an easy way of switching to another template language.
* Keep the good work :)
A question I'd love to see a good answer to. We've got Yesod, we've got Happstack, and also Snap. What are the major differences between them? Is one of them a clear winner, the way Django/Rails are in Python/Ruby respectively?
I have one question about yesod: how easy is it to switch templating languages? I had a look at it more than once, but hamlet always turned me off. Is it easy to switch to, say, hastache?
hamlet is by far Yesod's best feature. I have already ported it to Ruby (hamlet.rb) and Javascript (hamlet.js). Many users come with different pre-conceptions about what a good template language should be, but once they actually start using Hamlet, they love it. So honestly I am not 100% sure how much effort using a different template language is because not a single user has wanted to switch to an alternative. That…
Some points: * Generating migrations automatically when saved may cause some troubles while making large changes. It's a default setting? * Hamlet seems good but not so obvious for real-world designers. Would be great if you provide an easy way of switching to another template language. * Keep the good work :)
Some points: * Generating migrations automatically when saved may cause some troubles while making large changes. It's a default setting? * Hamlet seems good but not so obvious for real-world designers. Would be great if you provide an easy way of switching to another template language. * Keep the good work :)
I have one question about yesod: how easy is it to switch templating languages? I had a look at it more than once, but hamlet always turned me off. Is it easy to switch to, say, hastache?
hamlet is by far Yesod's best feature. I have already ported it to Ruby (hamlet.rb) and Javascript (hamlet.js). Many users come with different pre-conceptions about what a good template language should be, but once they actually start using Hamlet, they love it. So honestly I am not 100% sure how much effort using a different template language is because not a single user has wanted to switch to an alternative. That…
In your opinion.
>but once they actually start using Hamlet, they love it ... not a single user has wanted to switch to an alternative.
Hamlet is one of the major reasons we're using snap instead of yesod. Of the 5 devs here who worked on a test app in yesod, the most favourable reaction to hamlet was "well, I guess I could live with it if I had to". Just because we didn't come ask "how hard is it to use a decent template system with yesod" doesn't mean we love hamlet. We just tried out snap and happstack instead, where using whatever template engine you want is obvious and trivial.
A question I'd love to see a good answer to. We've got Yesod, we've got Happstack, and also Snap. What are the major differences between them? Is one of them a clear winner, the way Django/Rails are in Python/Ruby respectively?
They really have to change their website, but in particular that cheesy/glossy logo. It just looks awful.
* http://happstack.com/ * http://snapframework.com/
Design time!