Live data from Hacker News

Erlang will replace Java in the next 2 years as the standard for Enterprise Applications

voodootikigod.wordpress.com

1–10 of 40 posts

Re: Erlang will replace Java in the next 2 years as the standard for Enterprise Applications

#2
No, it won't. OO has ruled the roost in the so-called Enterprise space for nigh-on 20 years now. Java hasn't (yet?) fully displaced C++ in 10 years despite, for this specific class of application, have several clear advantages. This is as much cultural as technological. Large corporations have a morbid (and self-fulfilling) paranoia about staff turnover and have adopted technologies such as OO because it is far easier to manage a hundred average coders each of whom has a clear boundary (the object) than it is to manage 10 rocket scientists. The power of the functional paradigm comes with a steep learning curve, there's no way around that.

Re: Erlang will replace Java in the next 2 years as the standard for Enterprise Applications

#3
Java is still the standard language in the vast majority of CS programs. Lots of programmers entering the enterprise only know Java, and if they know more languages they definitely don't know Erlang.

Certainly demand for Erlang programmers will increase over time...

Re: Erlang will replace Java in the next 2 years as the standard for Enterprise Applications

#4
post #3

Java is still the standard language in the vast majority of CS programs. Lots of programmers entering the enterprise only know Java, and if they know more languages they definitely don't know Erlang. Certainly demand for Erlang programmers will increase over time...

History shows that the languages taught in CS and the languages used in industry don't need to be related at all. That the same language is popular in both at the same time is unusual.

Re: Erlang will replace Java in the next 2 years as the standard for Enterprise Applications

#5
post #2

No, it won't. OO has ruled the roost in the so-called Enterprise space for nigh-on 20 years now. Java hasn't (yet?) fully displaced C++ in 10 years despite, for this specific class of application, have several clear advantages. This is as much cultural as technological. Large corporations have a morbid (and self-fulfilling) paranoia about staff turnover and have adopted technologies such as OO because it is far easie…

The irony is that Erlang is so much easier than Java.

Re: Erlang will replace Java in the next 2 years as the standard for Enterprise Applications

#6
No it won't (this coming from someone who loves Erlang and has worked full-time with it for a year).

There has been way too much invested in both Java and conventional OOP for them to be displaced that fast. 2 years may be a long time in startup world, but in the enterprise world it's nothing.

Ruby has been growing rapidly for the last 3 years, and it's still nowhere as popular as Java. And Ruby's marketing has been way better than Erlang's.

Re: Erlang will replace Java in the next 2 years as the standard for Enterprise Applications

#8
post #6

No it won't (this coming from someone who loves Erlang and has worked full-time with it for a year). There has been way too much invested in both Java and conventional OOP for them to be displaced that fast. 2 years may be a long time in startup world, but in the enterprise world it's nothing. Ruby has been growing rapidly for the last 3 years, and it's still nowhere as popular as Java. And Ruby's marketing has been…

2 years may be a long time in startup world

It's actually not a long time in the startup world, either. The average life cycle in the valley for VC-backed startups from founding to exit is 7 years. There are always exceptions, of course. But two years isn't enough time, in general, for anything interesting to shake out--either in languages or in startup companies.

Re: Erlang will replace Java in the next 2 years as the standard for Enterprise Applications

#10
No.

Where are the plethora of libraries for Erlang that Java enjoy?

Java is great because you can stand of shoulders of people releasing brilliant libraries.

Who cares about Availability, Performance, Scalability ... if you can't ship?

Post reply on HN