«« Next » « Previous
«« Next » « Previous

Link Details

Link 34152 thumbnail
User 239150 avatar

By refcount
via cincomsmalltalk.com
Published: Aug 09 2007 / 02:34

Erlang is going to be a very important language. It could be the next Java. Its main problem is that there is no big company behind it. Instead, it is being pushed as an open source project. Its main advantage is that it is perfectly suited for the multi-core, web services future. In fact, it is the ONLY mature, rock-solid language that is suitable for writing highly scalable systems to run on multicore machines.
  • 28
  • 10
  • 3567
  • 1945

Comments

Add your comment
User 77421 avatar

rd112681 replied ago:

2 votes Vote down Vote up Reply

Scala, the next Erlang?

User 202522 avatar

gfxmonk replied ago:

1 votes Vote down Vote up Reply

"Its main problem is that there is no big company behind it."

erm.. wouldn't that be ericsson? Or do they just like to use it?

User 133619 avatar

murban replied ago:

1 votes Vote down Vote up Reply

...But I thought ruby was going to be the next Java? And before that, I thought it was going to be .NET / C#?... ;)

User 181930 avatar

jwenting replied ago:

-1 votes Vote down Vote up Reply

yep.
And Python before that.

Just the weekly "Java is dead" post, nothing to see.

User 51609 avatar

ak43706 replied ago:

0 votes Vote down Vote up Reply

Very interesting post. I wish it had a few examples. How about an expanded version?
I really like Java but I am waiting for something that's more 'event driven' and with better concurrency.

User 79499 avatar

in86835 replied ago:

0 votes Vote down Vote up Reply

I agree message passing is the way to go, AmigaOS relied heavily on asynchronous/synchronous message, to great effect, however I bet Java could do the same trick with little trouble and it probably has more libraries.

ak43706:
Event driven seems evil to me, because it can result in stalls in the event source (e.g. the misuse of AWT/Swing and Network events). Asynchronous message passing seems far better, because it minimises in stalls in the message source and is much better suited to constrained systems like AWT/Swing i.e. ANY change to Swing components should be via the asynchronous/synchronous AWT/Swing event queue, which is like a message queue, but with runnable objects, not just data, kind of like ORB.

Erlang has no major backer, seems still pretty much an unknown environment and Java has way too much momentum, far more that C and C++ ever had, even the more interesting parts of C#, Python and Ruby are having little effect other than to spur on the evolution of Java, so I see no significant threat to Java.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.