Hello Haskell Cafe, I just wanted to inform you that the Happstack project has shipped it's 0.1 release. For those of you who don't know, Happstack is the successor for the HAppS project. More details on the release can be found at http://blog.happstack.com/2009/02/03/happstack-01-released . Thanks for your time, Matthew Elder -- Need somewhere to put your code? http://patch-tag.com Want to build a webapp? http://happstack.com
Hi
Successor as in Happstack replaces HAppS entirely and all projects
implemented in HAppS should aim to port to Happstack - or successor as
in builds on the ideas in HAppS? Is HAppS now deprecated?
Thanks
Neil
2009/2/4 Matthew Elder
Hello Haskell Cafe,
I just wanted to inform you that the Happstack project has shipped it's 0.1 release. For those of you who don't know, Happstack is the successor for the HAppS project. More details on the release can be found at http://blog.happstack.com/2009/02/03/happstack-01-released .
Thanks for your time, Matthew Elder -- Need somewhere to put your code? http://patch-tag.com Want to build a webapp? http://happstack.com
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
Neil Mitchell wrote:
Successor as in Happstack replaces HAppS entirely and all projects implemented in HAppS should aim to port to Happstack - or successor as in builds on the ideas in HAppS? Is HAppS now deprecated?
The HAppS project has been abandoned, see http://groups.google.com/group/HAppS/msg/d128331e213c1031 . The Happstack project is intended to continue development. For more details, see http://happstack.com/faq.html . -- Jochem Berndsen | jochem@functor.nl GPG: 0xE6FABFAB
Jochem Berndsen wrote:
The HAppS project has been abandoned, see http://groups.google.com/group/HAppS/msg/d128331e213c1031 .
The Happstack project is intended to continue development. For more details, see http://happstack.com/faq.html .
So we've got HAppS, Happstack, WASH, Turbinado, probably others... Does anybody know how all these relate to each other? Where their strengths and weaknesses lie? It's nice to have choice, but without knowing what you're choosing between, it's hard to use it well.
andrewcoppin:
Jochem Berndsen wrote:
The HAppS project has been abandoned, see http://groups.google.com/group/HAppS/msg/d128331e213c1031 .
The Happstack project is intended to continue development. For more details, see http://happstack.com/faq.html .
So we've got HAppS, Happstack, WASH, Turbinado, probably others... Does anybody know how all these relate to each other? Where their strengths and weaknesses lie?
It's nice to have choice, but without knowing what you're choosing between, it's hard to use it well.
A comparative analysis of the 10+ Haskell web frameworks would be awesome. happstack, wash, fastcgi.., turbinado, perpubplat, riviera, salvia, kibro, ella, what was that one launched yesterday? *ah, yesod...
On Thu, Feb 5, 2009 at 6:58 PM, Don Stewart
andrewcoppin:
Jochem Berndsen wrote:
The HAppS project has been abandoned, see http://groups.google.com/group/HAppS/msg/d128331e213c1031 .
The Happstack project is intended to continue development. For more details, see http://happstack.com/faq.html .
So we've got HAppS, Happstack, WASH, Turbinado, probably others... Does anybody know how all these relate to each other? Where their strengths and weaknesses lie?
It's nice to have choice, but without knowing what you're choosing between, it's hard to use it well.
A comparative analysis of the 10+ Haskell web frameworks would be awesome.
happstack, wash, fastcgi.., turbinado, perpubplat, riviera, salvia, kibro, ella, what was that one launched yesterday? *ah, yesod...
That's a lot of frameworks to try & compare and I don't think any one person would have the time to do more than a couple, but perhaps we could all agree on some kind of non-trivial, but still simple, application that we could implement & deploy in the most natural way for each framework. It'd probably be easy to just point prospective framework users to the resulting series of blog posts elucidating the features of each. I'd vote for something like a trimmed down reddit clone, something that I'd expect everyone could do whether they deploy it via Apache or something that's part of the framework such as happstack-server. Cheers, C
On Thu, Feb 5, 2009 at 4:58 PM, Don Stewart
A comparative analysis of the 10+ Haskell web frameworks would be awesome.
happstack, wash, fastcgi.., turbinado, perpubplat, riviera, salvia, kibro, ella, what was that one launched yesterday? *ah, yesod...
Wow, that's a lot more frameworks than I realized... Anyway, I'm the guy who just started that new one, yesod. I don't think it's a good thing that there are so many of these unfinished web frameworks out there, and starting more is probably not that helpful. I did so because, as far as I can tell, none of the other frameworks out there are even remotely interested in the same goals as me. Happs(tack) seems to have thrown all convention about web frameworks out the window, which is fine, but not exactly usable in many conventional scenarios. Wash, fastcgi, and kibro all seem very low-level to me. Wash and fastcgi seem to correlate pretty well to ASP and FCGI.pm to me, which frankly don't provide much more than basic help in creating web sites. Turbinado seems to be the closest to what I would imagine as a mainstream framework. However, it is ignoring some features currently that I consider vital (correct me if I'm wrong): * Can run on a shared host. This means something like FastCGI, not its own server. * It's not aiming for any high-level Javascript/AJAX integration. I frankly think the generating plain HTML on the backend style is a little outdated at this point, and think we need to start exploring more advanced web development techniques. That said, if there's an existing web framework that has any interest in those two goals, I'd be happy to contribute to that instead of fracturing the community any more. It would be great if we could get some serious support behind a single framework. Obviously, I have more opinions than the two I just listed (I previously linked to a 14-point blog entry on the subject), but the others I would be willing to forego to achieve unity. Anyway, that's my plea. Sorry if it hijacked this thread too much. Michael
On Thu, 5 Feb 2009, Don Stewart wrote:
andrewcoppin:
Jochem Berndsen wrote:
The HAppS project has been abandoned, see http://groups.google.com/group/HAppS/msg/d128331e213c1031 .
The Happstack project is intended to continue development. For more details, see http://happstack.com/faq.html .
So we've got HAppS, Happstack, WASH, Turbinado, probably others... Does anybody know how all these relate to each other? Where their strengths and weaknesses lie?
It's nice to have choice, but without knowing what you're choosing between, it's hard to use it well.
A comparative analysis of the 10+ Haskell web frameworks would be awesome.
happstack, wash, fastcgi.., turbinado, perpubplat, riviera, salvia, kibro, ella, what was that one launched yesterday? *ah, yesod...
I'm afraid that http://haskell.org/haskellwiki/Applications_and_libraries/Web_programming has become less important since all people upload their stuff to Hackage and get automatically indexed and visible this way. However this Wiki page could be used by Web framework authors to advertise their frameworks, read how other authors advertise their work and adapt the own advertising accordingly. This might work like: "My framework can do X, but I didn't mention it, because I thought it is trivial. However since the others find X important, I'll add that to my feature list, too." "I see others support Y. I never thought about that. I'll add it to my ToDo list." "I see others solve problem X the way Y, where I thought my way Z would be the only one. So I'll mention that I solve it by Z and why I did not choose Y.")
participants (8)
-
Andrew Coppin -
Creighton Hogg -
Don Stewart -
Henning Thielemann -
Jochem Berndsen -
Matthew Elder -
Michael Snoyman -
Neil Mitchell