1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Any experience with Erlang?

Discussion in 'General Programming Chat' started by amazonian raider, Jul 12, 2012.

  1. amazonian raider

    amazonian raider Junior Member

    Joined:
    Mar 6, 2012
    Messages:
    114
    Likes Received:
    23
    I'm working on some custom tools for my arsenal, and was considering taking a dive into functional programming with Erlang to see if I can pick up some speed on multi-threading. From what I've been reading, Erlang has a significant leg up in running concurrent threads vs any of the OOP languages.

    I'm curious to hear if anyone on here has any experience with Erlang (or other FP languages), any tips, or know of any good resources that I might not find right away just using Google?
     
  2. kiggd

    kiggd Junior Member

    Joined:
    Apr 28, 2012
    Messages:
    116
    Likes Received:
    44
    Erlang is a great language in that you can implement concurrency in your application very rapidly. Now do keep in mind the speed of each concurrent thread isn't typically as quick as a Java or C++ thread.

    I'm no erlang expert (I've worked with some), but I can tell you that it's typically used to run on a server not a client device.
    But it DOES scale (hell erikson used it)
     
    • Thanks Thanks x 1
  3. amazonian raider

    amazonian raider Junior Member

    Joined:
    Mar 6, 2012
    Messages:
    114
    Likes Received:
    23
    Thanks for the input! I've been working through a book on Erlang the past few days and while I haven't dug very deep into the specific libraries I'll be using, I think this will be a good fit for this specific project at least. I'm pretty impressed with how simple the concurrency is to implement. I honestly hadn't experimented with threads in other languages but Erlang makes that part really simple.

    At some point, I'll have to try a project with threading in another language so I can get a better comparison of the two, but for now I think Erlang is the way I'm going to go with this project.

    This particular project is (hopefully) going to be run on a server at a large-ish scale. So your comment confirms that I'm headed on the right track. I also think it's pretty sweet that I'll be able to do system updates without having to shut the program down. That's not an absolute necessity for me, but it will sure remove some hassle if this thing works like I'm expecting.