Ergo: Erlang/OTP patterns implemented in Golang
There was another recent Erlang post which posited the suggestion that the <i>power</i> of erlang was not in lightweight processes and message parsing, but in generic components erlang calls <i>behaviours</i>. These generic patterns are what allows for building reliable distributed systems, and Joe Armstrong wrote a PhD thesis about it.<p>I gave an anecdote of having built a c++ framework that unwittingly followed the same principles for “big corp” long ago (convergent design), and posited that the same concepts could probably be built in any language. Here it is for <i>go</i>. So is it a good thing?<p>Previously I suggested it would be good to capture these core concepts in standardized libraries for a range of languages, but now I am not so sure. The problem I have is that as you start looking at these higher level patterns involving distributed computing, the landscape of frameworks seems to explode. Is this because the erlang&#x2F;otp concepts are insufficient or outdated?