[erlang-questions] Erlang is the best choice for building commercial application servers

Tim Watson <>
Mon Mar 12 15:40:30 CET 2012


On 12 March 2012 13:30, Matthew Evans <> wrote:
> Yes, this is very true.
>
> But as I mentioned before, most large Java applications aren't "just Java".
> They include Java SE or EE, Spring or some similar framework, Hibernate or
> some other database access library, a DB itself, Dozer to do object to
> object mapping, GWT to do any kind of GUI and so on. Then once this is done,
> you now need Maven to bring it all together and Eclipse because it's so
> darned complex there is no way that Vim or Emacs will work. On top of this
> all of this stuff is glued together by pages of XML. You have a massive
> learning curve for all of this, worse still any 2 companies are probably
> using a different combination of said libraries/frameworks. My own company
> is using some of the above, and even the expert on the topic struggles from
> time to time.
>
> Although Java will certainly be around for 10 years, there is a good chance
> that on any project with a lengthy shelf-life some of these libraries
> would've died or been replaced with something more "shiny". Finding
> developers in 10 years who know Spring version X, and Hibernate version Y
> will also be hard. So you certainly have the same issues with Java apps that
> you do with Erlang. I would actually say Erlang is much better here since,
> although there are lots of 3rd party libraries out there, 99% of what most
> people need is all included out of the box. Effectively with Erlang the
> learning curve is a one off effort.
>

Personally I do agree with this, but sadly it don't find it to be a
particularly prevalent view in the wider world.



More information about the erlang-questions mailing list