4 ms·

So suddenly I need to worry about mutexs and two processes accessing the same data. As an Erlang programmer that smacks of Erlang done wrong to me. I don't wan

• adgar 15y ago
  > So suddenly I need to worry about mutexs and two processes accessing the same data. Only if you're implementing higher-level concurrency primitives and want to maximize performance. Did you completely ignore the context in which mutexes were mentioned in those slides?
  • rdtsc 15y ago
    To be fair the slides never really makes any comparisons with Erlang instead just used an inflammatory title, so it is understandable if responses are a little hand-wavy. It just goes along given the level of discussion.
    • adgar 15y ago
      > To be fair the slides never really makes any comparisons with Erlang instead just used an inflammatory title, so it is understandable if responses are a little hand-wavy. Totally true - the Erlang too-dumb-to-be-a-cheap-shot was unwarranted. There are responses already posted in this thread along the lines of "This doesn't have anything to do with erlang at all" and they're completely justified. The comment I responded to was calling out specific details out of context and making silly comparisons from there. That's all.