Linked by Thom Holwerda on Thu 30th Oct 2008 12:53 UTC, submitted by CPPfanboy
Thread beginning with comment 335839
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
That's a pretty broad statement.
Yes, indeed. I did of course not mean the obvious; attempting to write the next Crytek engine in Erlang just to be able to peak all your cores, and then let it borrow some from your friends as your machine just isn't cutting it. For some things, there simply is no replacement for C++. The same goes for Erlang.






Member since:
2005-11-11
That's a pretty broad statement.
I've done programming with threads in C++, Java and even Python. Some of it could have been done in Erlang and other things I wouldn't dream of doing in Erlang.
If I concurrency was only about getting the best performance out of your machine at any cost, then you might be right, but there are lots of situations where it's just not worth it to use a tool like Erlang.