[erlang-questions] Misultin EOL

[Barco You]

>my intent here is to avoid duplication of efforts, both for the
contributors of the community (often reporting the same bugs in both
repositories) and for the developers, which now have an hard time in
deciding which way to go.

>i just wanted to clear the way for a single webserver library, and cowboy
seems to have much more developer time to actually maintaining it.


What's the logic behind forgoing a better one to support another with the
purpose of avoiding duplicate efforts? Why not contributors come to help
migrate the productions on those over-hyped frameworks to on the
proven-best one?

No matter how, I like Misultin very much for its high performance,
simplicity and advanced concepts. If it would really go I would be very sad
and I believe many others in this community too.

Let's find a better way to contribute to our community better!

Regards,
Barco
On Fri, Feb 17, 2012 at 10:09 AM, Steve Davis <
steven.charles.davis@REDACTED> wrote:

> Hi Roberto,
>
> I'm a bit confused by this whole thread...
>
> I'm agreeing with Jesse that since Misultin is open source, it's not
> really in your control to "stop development" if the interest is there
> elsewhere to push it on?
>
> I'm also agreeing with Steve that I've not seen any demonstration that
> yaws is somehow "lacking",
>
> For me, the last interesting benchmark that demonstrated anything
> graspably real was "yaws vs apache".
>
> A really interesting benchmark for today's "web server" would be, if
> someone were willing to engage in a non-trivial effort, to make a
> comparison of a full-fledged web application with full session
> management and routing capabilities. Note that this would truly test
> the appropriateness of the server's http APIs as well as the base
> response. That kind of benchmark, for me, would seem more appropriate
> and useful according to the epoch.
>
> Best regards,
> /s
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120217/e2ef4e27/attachment.htm>