3 ms·
I'm talking about large applications. In C++/Java large amount of code is defensive programming, locking and synchronization - you don't need it in Erlang. Di
by nivertech 16y ago
I'm talking about large applications.
In C++/Java large amount of code is defensive programming, locking and synchronization - you don't need it in Erlang.
Distribution - even if you use CORBA/RMI you still have to write a lot of plumbing code in C++/Java. In Erlang it's comes almost for free.
Binary protocols handling - very succinct in Erlang with binary syntax and verbose in C++/Java.
- killedbydeath 16y agoI am not too familiar with Erlang, but I am very familiar with Python and C++. And you put Erlang between Python and C++ by verbosity, so I made my conclusions accordingly. Also, synchronization and locking (with mutexes) are not the only approach to parallelization in C++. You can immutable objects, futures and other high level concepts. But Erlang has to be really nice for the stuff it was designed for, I have no doubts about that.
- thesz 16y agoYou're wrong. The code ratio is about 1/3, for large applications. http://www.slideshare.net/Arbow/comparing-cpp-and-erlang-for-motorola-telecoms-software http://www.slideshare.net/Arbow/comparing-cpp-and-erlang-for...