(Prolog + LISP + Erlang) with integration issues versus C++

Dev Functional <>
Sun Sep 4 11:35:17 CEST 2005


Hello all

I would sincerely like to thank all of the people who responsded to my mail.

Here are the details of the discussion and decisions made.

1)  It was pointed out that while each language will have merits and strength,
     however, together they would have both interop (performance) and
maintenance
     issues.

2)  It was stated that it is better to fight with the nuances of one language,
     rather than drool on the strength of each of them independently and 
     then face licensing issues, interop issues, performance issues, support
     issues , not to speak of the maintenance.

3)  It was pointed out that today even Ericcsson does not use Erlang for its
     new product development. Why ?

4)  The following products of Ericcsson are written in C++
     TelORB
     distributed RAM database, the base for the TSP application
     server platform
     TDMA-CDMA HLR
     GSM-TDMA-CDMA mobility gateway
     AAA server.

5)  It was pointed out that clisp has GPL licensing and no money should be 
     wasted on acquiring software licenses (eg. Franz)

6)  It was pointed out that Prolog, CLISP are themselves interested in C !
     So, if there is a smart idea present eg. backtracking, we can see the 
     implementation and use it in the code. There is no need to take
the complete
     load of the language, since we don't want all the features any way.

7)  RPC and message passing related weakness in Erlang can cause security 
     vulnerability issues.

8)  High performance in computation, high responsiveness in network i/o,
     aync and disk i/o is mandatory.

     The performance slide related to yaws was mentioned and the management
     wondered why the world hasn't moved on to yaws by ditching
oh-so-slow Apache ?

8)  The management has decided to organize 4 week long formal rigorous training
     in C++ and Template Programming. There will be sessions in competency
     building in tools like gprof, gdb, g++4, gcc4 etc.

9)  The decision has been taken by the management and the tools to be used are 
     - C++ (user land), g++4
     - C     (kernel land) gcc4
     - STL
     - Boost Library
      There is no license fees to be paid to anybody.

10)  All storage related standards have types defined in C and it makes sense
       to have the programmatic representation as close as possible to
the standard.

11)  The management also highlighted that if the languages so far used
(prolog,lisp,erlang)
       were so great then the capitalists would have grabbed them up
long time ago
       and made lots of money by now by developing and selling products.
       So, either the capitalists are fools or the current development team !

       It was also pointed out that Google does lot of work related to
information
       retrieval, inference, distributed computing over thousands of
compute nodes
       but does not use Erlang ! Why ?

In the final analysis, the project will proceed with the above made decisions
and I will need to abide by these decisions if I am to keep my job.

Once again thanks to all the people on this list, who tried to help me out.

thanks
Dev.



More information about the erlang-questions mailing list