[erlang-questions] The quest for the perfect programming language for massive concurrency.
Sat Feb 1 20:11:03 CET 2014
I would add one more feature of Erlang that I don't think has been
mentioned: the community is one of the best you will find in all of
To illustrate, please refer to this email thread, which I came across:
Here you have someone who is asking very honest questions about Erlang
vis-a-vis other languages. In many communities, this sort of question,
while not intended to do so, would spark a series of flame wars and
religious zealotry. But this question, on the Erlang list, brought
forth some of the most brilliant and thoughtful contributions to
important problems in software I've ever seen.
What is this worth in your comparison of languages?
As an aside, I think this particular email thread, which I came
across, should be printed without editing as a pamphlet and handed out
at user groups and software conferences as a treatise on core
principles of language and tool design and civil discourse. If others
are willing to join me, I would consider shaving my head and wearing
brightly colors robes and do this.
On Sat, Feb 1, 2014 at 12:07 PM, Tim Stewart <> wrote:
> On 01/31/2014 01:03 PM, Attila Rajmund Nohl wrote:
>> 2014-01-30 kraythe .<>:
>>> >The tools are, well frankly, garbage. Sorry, in 2014 to be pushed back
>>> > to
>>> >coding with VIM and makefiles is primitive. Rebar is crytptic and just
>>> > the
>>> >pet project of a guy on GIT. Compared to Gradle, Maven and even (though
>>> > I
>>> >don't care for it much) SBT, rebar is ... lacking. I want to spend time
>>> >working on my business logic, not fighting tools. There are plugins for
>>> >eclipse and intellij but they have minimal functionality and i keep
>>> >reverting back to vim.
>> In some sense you're right, in some sense not. In a previous project
>> our "integration build" was quite slow, when behaviors were modified,
>> everything was recompiled because our Makefiles lacked proper
>> dependencies. So some automatic dependecy generator would be nice (I
>> don't know what rebar does). On the other hand in the normal
> The compile module (http://erlang.org/doc/man/compile.html) supports
> generating Makefile rules to track header dependencies via the `makedep'
> option. You can also invoke this via erlc's `-M' option.
> This may not be the solution to Attila's integration build dependency
> problems, but I feel it is worth mentioning in the context of this thread.
> Tim Stewart
> erlang-questions mailing list
More information about the erlang-questions