[erlang-questions] Misultin EOL

Matti Oinas <>
Sat Feb 18 21:35:23 CET 2012


On 02/18/2012 09:55 PM, Steve Vinoski wrote:
> If people want
> to contribute they should instead be working either within existing
> projects like Yaws, or perhaps better yet, within Erlang/OTP itself,
> in both the Erlang code and the C code, to improve scaling and
> performance at that level. Speed up the HTTP parsing within Erlang,
> for example.
Steve has a really good point in that we should concentrate to improve 
the existing and as few as possible different implementations and if 
possible the one included in Erlang/OTP. Sometimes something new has to 
be created to demonstrate the benefits and to make development go faster 
but these new solutions shouldn't be recreated from the scratch just to 
alter a minor part of existing solution. Instead improvements should be 
made into existing code. If the old code isn't fast or good enough then 
fix it instead of writing a new one. Open source can only help if we are 
using existing solutions and trying to make them better instead of 
trying to create a new and better one and leaving existing code unfixed.

I have written partially working web server and other common 
applications/libraries myself but just for learning purposes and when I 
have come to a conclusion that I have learned what I wanted then I just 
move the codes to my backup HD and forgot they even exist. No one would 
benefit anything from these codes because everything have been done 
before and there exists good solutions to these problems allready. 
Situation would have been different if I would have created a totally 
different and good solution to existing problem. Then the code should be 
published.

I'm not saying there should only exist one solution to every problem but 
there shouldn't exist two or more allmost identical solutions to same 
problem. First try to contribute to existing solution before creating a 
new one.

Matti



More information about the erlang-questions mailing list