[erlang-questions] Misultin EOL

Tim Watson <>
Fri Feb 17 23:57:07 CET 2012


On 17 February 2012 22:42, Andrew Berman <> wrote:

> Tim,
>
> I think a comparison between the Java app servers is not really accurate.
>  The reason I say that is that most have commercial support.  Tomcat might
> be the only one without commercial support, but it's the reference
> implementation and has plenty of books about it.  As far as I know with all
> the other popular ones there is some company who's willing to support it.
>  I think that's a big difference here between comparing Java app servers
> and Erlang servers.  Misultin is completely open-source with one man
> supporting it and no commercial support.  I'd much rather see fewer servers
> with better support and possibly commercial support than many with little
> support.
>
>
Yes ok, you make a very good point there. I hadn't thought about that, and
on a few minutes reflection, I think you're quite right.


> I do agree completely that Erlang needs a consistent servlet-like API.  It
> would certainly help a lot.
>
>
Yes. There database libraries need this too. Java might be pants, but there
are a few good things we can learn from it, and consistent APIs are one of
them.


> I'd be keen on simple bridge if the Erlang guys would just come out and
> say if they support parameterized modules or not.  If they don't, just get
> rid of it.  What's the point of having something in a language if it's not
> going to be supported (but that's a different topic)?
>
>
Yes indeed, same here. Personally I actually find them rather unintuitive,
but I'd use them more readily in other people's libraries if they were
properly supported. We've actually got Misultin running in production and
it's been great, so it's not that I'm completely allergic to parameterised
modules, just that I would prefer not to have them in an API.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120217/8f7d21e2/attachment.html>


More information about the erlang-questions mailing list