10:56:37 <HugoDaniel> http://hackage.haskell.org/package/yesod-0.5.4
10:56:40 <HugoDaniel> im looking at this
10:56:46 <HugoDaniel> seems like it is the nicest thing ever
11:01:36 <HugoDaniel> after looking at some examples i can tell i prefer using happstack
11:08:52 <HugoDaniel> maybe ill write a comparison
11:09:18 <HugoDaniel> of happstack, snap and yesod
11:09:30 <HugoDaniel> altough yesod seems to be a different kind of tool
11:15:58 <HugoDaniel> "This is different than the approach taken by many other web frameworks. In Yesod, by default, different request methods have different handlers. This makes it easier to write properly RESTful web applications."
11:20:06 <Entroacceptor> you can do that easily with happstack, too
11:20:10 <HugoDaniel> yes
11:20:12 <HugoDaniel> indeed
11:20:18 <HugoDaniel> they have a nice concept though
11:20:24 <HugoDaniel> the concept of "representations"
11:21:46 <HugoDaniel> its like views, each datatype has several "representations", be that xml, json or html or plaintext... they decide which "representation" to use by the http accept header
11:22:12 <Entroacceptor> oh, that's cool
11:22:14 <HugoDaniel> they also have their own templating language, which they dont enforce
11:22:21 <Entroacceptor> and they have a model...
11:44:51 <Entroacceptor> the representation stuff looks really nice, yes
12:02:50 <Tennon> Sup doods, how's it Haskelling?
12:08:50 <Entroacceptor> driving me even more insane
14:12:04 <stepcut> HugoDaniel: I have done that sort of thing in happstack. Not sure how it compares. I have a type, data SiteResponse = ..., which I used to build all the responses the site will return. And then I have a special form of toResponse which can convert it to different output formats
14:27:59 <HugoDaniel> :D